amrisi / amr-guidelines

240 stars 86 forks source link

Unification Adjectives #137

Closed timjogorman closed 9 years ago

timjogorman commented 9 years ago

Hi all! I wanted to bring up the topic of adjective annotation, as unification day approaches. Sorry for getting this out barely before the call.

I did some scouting of the AMR data for re-annotation. The good news is that we have pretty good coverage over adjectives! That's the bad news too -- annotating everything we have a frame for will take a lot of work.

By my amateurish count, of all the concepts with :mod relations in the last LDC release, we have:

I'm really really sympathetic to the idea of not doing additional work on adjectives. My main thing is that if an annotator sees an adjective, I'd like it to be clear what their next step is, without having to guess about its lexical properties. That's the appeal of our current, sometimes shallow, ":mod" treatment -- it's a single step.

The additional thing to note with the adjectives is that many have a single argument that would modify the "head" of the adjective (often arg1/proto-patient) -- "new.01", for example, has "arg1" for who/what is new, and "arg2 new to what?". If one was able to just say "grab the default, proto-patient role if there is one", that gets behind many of the same assumptions as "mod", right?

I imagine us having a shortcut function -- let's say ":ppt" -- that does the obvious when that's deterministic and alerts the annotator if there isn't. Specifically:

I don't know if that's linguistically feasible or tractable for the editor, but wanted to throw it out there.

Additional arguments against leaving 1-roleset, 1-role adjectives these as "mod":