Coder Social home page Coder Social logo

Comments (4)

nschneid avatar nschneid commented on August 26, 2024 1

@ULFULF can confirm but I believe the annotation docs are more up-to-date than the guidelines.

have-value-91 occurs in only one release AMR (in the BioAMR corpus).

from amr-guidelines.

uhermjakob avatar uhermjakob commented on August 26, 2024 1

Thanks for pointing this out. Some of these pairs are valid role/reification pairs, some "roles" are only shortcuts.

Valid AMR role/reification pairs:

Not valid AMR roles; used only as shortcuts in the AMR Editor:

  • :cause cause-01
  • :cost cost-01
  • :employed-by have-org-role-91
  • :meaning mean-01
  • :role have-org-role-91
  • :subset include-91
  • :superset include-91

Note: The shortcuts' purpose is to make life easier for human AMR annotators. The AMR Editor automatically and instantly expands these shortcuts from pseudo-roles to their AMR reifications.
So the shortcuts will not appear in the AMR corpus.

In the table at the bottom of https://www.isi.edu/~ulf/amr/lib/roles.html these were marked as shortcuts
by being colored grey and indicating the "shortcut" nature upon mouse-over. Probably not obvious enough, so I now explicitly mark them as "shortcut only".

Updated: https://github.com/amrisi/amr-guidelines/blob/master/amr.md, https://www.isi.edu/~ulf/amr/lib/roles.html

from amr-guidelines.

goodmami avatar goodmami commented on August 26, 2024

Great, thank you for clarifying and for updating the docs and guidelines. While we're on the subject, here are a few more things I noticed (after originally filing this issue):

  • It appears that the arguments of :accompanier are backwards (should be domain=ARG1 and range=ARG0, I think). I only checked the argument order of a few roles, so there may be other occurrences.
  • :beneficiary has two reifications in the docs (benefit-01 and receive-01) but only one in the guidelines
  • While many(roles)-to-one(concept) mappings seem unambiguous because they select different arguments (such as :subset and :superset), the one-to-many mappings (:beneficiary and :poss) are ambiguous. In other words, if the two concepts (benefit-01/receive-01 and have-03/own-01) have different meanings, then there is information loss when collapsed to a relation and information needed for reification. Are there guidelines for dealing with these, or is it just up to the annotators intuition about which to use?

from amr-guidelines.

goodmami avatar goodmami commented on August 26, 2024

4.5 years later... My question above about :accompanier was resolved in #269 along with :example. Similarly, :poss was addressed in #262.

I'm not sure about the receive-01 reification of :beneficiary. I've been mapping it with domain=ARG2 and range=ARG0 following this frame: https://www.isi.edu/~ulf/amr/ontonotes-4.0-frames/receive-v.html.

I'll close this issue.

from amr-guidelines.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.