Comments (10)
FTR, only and just are advmod
in English, which doesn't use advmod:emph
.
There are language-specific documentation pages for advmod:emph
in Turkish and Tatar. I don't know if that reflects all treebanks in Turkish or just some of them.
from docs.
I would make it a dependent of time. There is a policy (that I only noticed recently) distinguishing "pure function words" that do not accept modifiers other than negation: these include case markers/adpositions and articles, and potentially other words. For English I would assume that demonstrative determiners should be considered pure function words. (As opposed to demonstrative pronouns, which can take relative clause modifiers, for instance.)
Looking at treebanks there are some quantifier determiners with modifiers like "yet another", "nearly all", "almost every". But I don't see any demonstrative determiners with modifiers.
from docs.
The pattern I am seeing in English treebanks is that prenominal "nearly all" is treated as a unit, but not prenominal "only this". This may have to do with the fact that "only" is a focusing modifier that applies to nominals in general, whereas "nearly" is a degree modifier of a quantity.
-
Only this book needs to be returned.
-
Only books that are overdue need to be returned.
-
Only my aunt's casserole was not finished in its entirety.
-
Nearly all books need to be returned.
-
Nearly 30% of student borrowers will see some relief with this policy.
-
*Nearly books that are overdue need to be returned.
But then we have to deal with the less common case where the modified quantity is not a det or nummod:
- Nearly the entire population of student borrowers will be helped by this policy.
- "nearly everyone"
- "nearly a quarter century"
The quoted ones are both treebank examples, and "nearly" modifies the head of the nominal ("everyone", "century"). So it is not a categorical rule that "nearly" never modifies the head nominal.
At the end of the day I don't think English UD has all the answers on determiners and determiner-related dependents in nominals, especially when it comes to various constructions for expressing quantity and measurement. So, take this precedent with a grain of salt.
from docs.
@iambusra, do you have thoughts on this?
from docs.
FTR, only and just are
advmod
in English, which doesn't useadvmod:emph
.
Does this pass validation, when you have an advmod
dependent on a noun or a number or an adposition?
from docs.
Yep, the validator does not look at subtypes except a couple of the semi-mandatory ones, and advmod
dependents of non-predicate non-modifier words is acknowledged in the guidelines: https://universaldependencies.org/u/dep/advmod.html
from docs.
I guess my question was more about advmod
modifying anything. So, for example, what about modifer words with advmod
dependencies—e.g., in only this time, would only be an advmod
dependency of this (a determiner), or it dealt with differently?
from docs.
I guess my question was more about
advmod
modifying anything. So, for example, what about modifer words withadvmod
dependencies—e.g., in only this time, would only be anadvmod
dependency of this (a determiner), or it dealt with differently?
If something is an ADV
, it is required to depend as advmod
, also in this case. I think that using advmod:emph
is a useful distinction, which also points to the fact that this is not really a "usual adverb". In general, if we annotate sadece or else as an ADV
, there are no problems in making it depend as advmod
, on whichever other part of speech, and this is probably the best solution (instead e.g. of identifying a DET
sadece for noun phrases vs. an ADV
sadece for predicates).
Since it is annotated as a function word, I also agree that its relation is with the head of the noun phrase, so dakika or time in current examples. But it might also be otherwise: in something like nearly all persons, I would propend towards advmod:emph(
all,
nearly)
. I do not think that determiners are "pure function words", which seems to refer to the multifarious class represented in UD by CCONJ
/SCONJ
/ADP
/PART
.
from docs.
, there are no problems in making it depend as
advmod
The question wasn't about the deprel but the head.
in something like nearly all persons, I would propend towards
advmod:emph(
all,
nearly)
.
This is my inclination as well, but @nschneid suggests this isn't attested in (English?) treebanks.
Is there at least consensus that this is a reasonable annotation of such structures?
Since it is annotated as a function word, I also agree that its relation is with the head of the noun phrase, so dakika or time in current examples.
I don't fully get why this should be different from nearly all persons.
from docs.
, there are no problems in making it depend as
advmod
The question wasn't about the deprel but the head.
I was referring to this in the original post:
But that raises what kind of relation it should be. It's not quite an
advmod
because it can be a dependent on pretty much any part of speech (like only and just in English).
With regard to the head
Since it is annotated as a function word, I also agree that its relation is with the head of the noun phrase, so dakika or time in current examples.
I don't fully get why this should be different from nearly all persons.
I would also give an explanation like the one by @nschneid , but the more I think about it, the less obvious it is 🤔
Probably they interact with the other modifiers: degree modifiers can modify others, and focalisers can focus anything.
But it might as well be that I was making a blunder. Looking at these examples
- Nearly the entire population of student borrowers will be helped by this policy.
- "nearly everyone"
- "nearly a quarter century"
the position of nearly "outside" the determiner seems to point to it modifying the whole phrase, and so attaching to the head. Now we might talk about how much lexical or functional terms like entire (maybe PronType=Tot
?) or quarter (a numeral) are, but the whole phrase is to be considered "scaled". This happens also for focalisers, as in only this book...
The reason for not being able of saying nearly books is that this expression is not quantified somehow. But I would no longer say that this means that if a quantifier is present, nearly attaches to it.
So personally I would correct my previous statement and lean towards attaching elements like nearly, only, etc. always to the head. In some cases, this might indirectly lead to reconsidering annotation of some elements (entire, quarter...)
from docs.
Related Issues (20)
- Treatment of split "what a ((ADJ) NOUN)" construction in Low Saxon and Dutch HOT 16
- Dative Subjects Saraiki HOT 5
- Misidentified Lemmas in Spanish HOT 1
- clausal appos HOT 36
- Flat:foreign with Typo=Yes HOT 3
- acl vs xcomp vs advcl HOT 1
- Deprel of list item enumerators HOT 11
- English nominal subtypes: merge :npmod and :tmod as :unmarked HOT 18
- Create treebank without syntactic dependencies HOT 2
- How to document script used for the data in treebank? HOT 7
- Some Broken or missing treebank links HOT 4
- NPs in head-marking languages HOT 19
- Standardizing ExtPos (at least for fixed expressions) HOT 36
- New enhanced dependencies - Propagation of nsubj for ccomp and advcl in pro-drop languages HOT 3
- Annotation of Classifiers in the Egyptian-UJaen Treebank HOT 33
- English mischievous nominals involving names and numbers HOT 7
- Repository for new treebank HOT 1
- Transitive vs intransitive verb features? HOT 1
- `as X as` expressions as `fixed` with ExtPos - what qualifies? HOT 8
- Ellipsis in UD HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docs.