-
Notifications
You must be signed in to change notification settings - Fork 43
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
Inconsistent UPOS for anyone, someone and everyone across English treebanks #372
Comments
In PTB they are considered nouns, but according to https://universaldependencies.org/u/pos/PRON.html they should be considered PRON in UD. Since this is a closed class I don't see that divergence as a problem. See also #230 re: feats |
Full table at https://universaldependencies.org/en/pos/PRON.html#indefinite-pronouns EWT query for all except "no one": http://universal.grew.fr/?custom=634adbc7a092f I will fix the 5 errors in EWT. |
…me Enron acronyms, including it->IT; validator issue with feat sorting on 2 tokens
…; expect PronType=Ind for all indefinite pronouns (#230)
I'm not passionate about upos, if those guidelines are meant to be/can be made consistent across languages, let's do it. I'll fix GUM/Reddit. |
Looking at that page I think 'everything/one' should not be PronType=Ind, it should be PronType=Tot, no? |
I'm not familiar with "indefinite" versus "total" versus "negative" pronouns being a distinction in English grammar. See this table, for example. @dan-zeman was that intended mainly for determiners? |
That table has a column 'universal' - I think that's what is intended here. GUM uses https://gucorpling.org/annis/#_q=UHJvblR5cGU9IlRvdCI&_c=R1VN&cl=5&cr=5&s=0&l=10 |
Ah, I see here that |
OK I think this is fixed for EWT and GUM (the treebanks maintained at Georgetown). Consider opening an issue in the repo for PUD. |
These 3 lemmas (anyone, someone and everyone) are annotated inconsistently (either
NOUN
orPRON
) in different English treebanks.In 2.10 data, the UPOS tags used are:
NOUN
PRON
The text was updated successfully, but these errors were encountered: