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
The most frequent incorrectly assigned dependencies #1649
Comments
This is a good idea for improving the parser on your data. You might want to sign up for the beta of our annotation tool Prodigy: https://prodi.gy . What I did before Prodigy was to have a text file and easy macros that would mark an entry correct or incorrect and move to the next like, so that decisions would be made in a single keypress. This will work fine for your task. |
Thank you very much for your reply! Prodigy is great! But there is no possibility to annotate syntactic dependencies in the moment, right? When is this option available? |
@redstar12 Thanks! At the moment, no, but we're definitely planning a displaCy-style annotation interface as well. For this use case, you're only going to be looking at one dependency at a time and collecting simple, binary feedback. So you could just add a string version to your data, and create annotation tasks that look like this: {"text": "like → nsubj → I", "data": {"head": "like", "dep": "nsubj", "child": "I", "freq": 40302}} You can then and use the Btw, if you do want to generate displaCy visualizations for your extracted dependencies, for example so you can inspect them better, you can use the built-in deps = {'words': [{'text': 'I'}, {'text': 'like'}, {'text': 'green'}, {'text': 'apples'}],
'arcs': [{'start': 0, 'end': 1, 'label': 'nsubj', 'dir': 'left'}]}
svg = displacy.render(deps, style='dep', manual=True) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
How can I find out which incorrectly assigned dependencies are the most frequent?
The text was updated successfully, but these errors were encountered: