Open timjogorman opened 7 years ago
For choice questions, I think include-91
makes me squeamish because of the or
layer. There is something noncompositional about allowing each of the or
clauses as the possible responses.
Consider:
Who was a teacher or professor that you loved?
(l / love-01 :ARG0 (y / you) :ARG1 (a / amr-unknown :ARG1-of (i / include-91 :ARG2 (o / or :op1 (p / person :ARG0-of (t / teach-01)) :op2 (p2 / professor)))))
The expected response would be someone's name. That's a different question from "Was it a teacher or a professor that you loved?" For which I could see something like:
(l / love-01 :ARG0 (y / you)
:ARG1 (a / amr-unknown
:mod (c / choice-value
:op1 (p / person :ARG0-of (t / teach-01))
:op2 (p2 / professor))))
Or even:
(l / love-01 :ARG0 (y / you)
:ARG1 (a / amr-unknown-choice
:op1 (p / person :ARG0-of (t / teach-01))
:op2 (p2 / professor)))
From today's call, it seems we're converged on :polarity amr-unknown
, :polarity truth-value
, and for choices:
Do you want tea or coffee?
(w / want-01 :ARG0 (y /you)
:ARG1 (a / amr-choice
:op1 (t / tea)
:op2 (c / coffee)))
Was it a teacher or a professor that you loved?
(l / love-01 :ARG0 (y / you)
:ARG1 (a / amr-choice
:op1 (p / person :ARG0-of (t / teach-01))
:op2 (p2 / professor)))
I retrofitted the bulk of yes-no-questions in the AMR release corpus
by extending and running my repair-amr script which now automatically
updates any top-level :mode interrogative
to :polarity (a / amr-unknown)
[or a2/a3/... -- whatever the first unused variable is].
Two exceptions:
(o / or :mode interrogative :op1 (...) :op2 (...))
:mode interrogative
and :polarity -
such as for Isn't he hungry? where we probable want to avoid(h / hungry :polarity (a / amr-unknown) :polarity - :ARG1 (h2 / he))
Isn't he hungry? is similar to He is hungry, isn't he? which we annotate as:
(h / hungry :ARG1 (h2 / he) :ARG1-of (r / request-confirmation-91))
I updated sub-sentences directly under top-level multi-sentence analogously,
as well as (most) sub-AMRs directly under top-level and/or/contrast-02 if there is no :op1/:ARG1
(typical for yes-no questions that start with "and/or/but").
Among other things, this avoids updates to AMRs such as
(or :op1 (... :mode interrogative ...) :op2 (... :mode interrogative ...))
which often signal a multiple-choice question.
Number of updates performed: 1820 (consistent with Tim's estimate of roughly 2000).
Another tricky case:
Racially insensitive? DF-199-193600-660_5903.5
(s / sensitive-03 :polarity - :mode interrogative
:ARG1 (r / race))
This is based on #193 and #185 -- look back at those for more background. I'm just posing an estimate for how much this would cost to actually retrofit.
The rough profile of the
:mode interrogative
instances:Proposal
:mode interrogative
instances with "whether" or "if" into the truth-value trick, or some other treatment (cost: about 500 quick/easy retrofits; I'm assuming that's too complicated to do automatically):mode interrogative
after that. I'd propose doing choice questions using my proposal from #185, but it's not a settled issue. (cost: 200 retrofits).All told, assuming that people are manually changing complements and that each AMR takes 1 minute, it would require about 15 hours of annotator time to retrofit, assuming that the top-level instances of ":mode interrogative" could be changed automatically. If that needs to be done manually, this would roughly 46 hours of annotator time.
Proposed Treatments
I'm assuming the general proposal from Kevin, with my analyses for "whether" clauses and choice questions; I don't think that these are settled issuse. If those with doubts (I think Nathan and Kira) could produce a separate proposal (ideally re-stating my examples here) we could compare the two.
polarity amr-unknown treatment:
truth-value trick:
choice questions