Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for the Web Treebank style of traces #1

Open
jkkummerfeld opened this issue Dec 6, 2017 · 4 comments
Open

Add support for the Web Treebank style of traces #1

jkkummerfeld opened this issue Dec 6, 2017 · 4 comments
Assignees

Comments

@jkkummerfeld
Copy link
Owner

More recent LDC data has annotated traces like this:

(S
  (NP-1 (NNP Bob) )
  (VP (VBD tried)
    (S
      (NP-1 (-NONE- *PRO*) )
      (VP (TO to)
        (VP (VB wash)
          (NP (PRP himself) ))))))

The format converter should be updated to handle this format too.

@Fantabulous-J
Copy link

It seems that the format converter doesn't handle some cases in OntoNotes 5.0 as you mentioned above. Do you plan to update the converter?

@jkkummerfeld
Copy link
Owner Author

I don't have any immediate plans to implement this (too busy with other work). Depending on what you need to do, the code does work for some cases. For example, it can read in the format and (1) print out one-line or multi-line versions of parses, and/or (2) apply most of the edits, and/or (3) filter by sentence length.

The main things it can't do are:

  • Read ontonotes and print to my split head format
  • Read my split head format and print to ontonotes format
  • Read PTB and print ontonotes format

@Fantabulous-J
Copy link

Yeah, I can successfully read the parse tree in PTB format and convert it to your split head format on most cases of Ontonotes 5.0. It only fails in some rare cases. Maybe I can do it manually. But overall, thanks for your contribution

@jkkummerfeld
Copy link
Owner Author

Probably the easiest way to do this would be to write something to preprocess the parses, moving the indexation to the child node where appropriate (and then similar code to reverse that when going the other way). That said, there may be more complex examples than the one I included above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants