-
Notifications
You must be signed in to change notification settings - Fork 42
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
New analysis for multiple/nested subjects due to clausal predicative complement #310
Comments
|
Clarification: should it be considered an outer subject if the copular predicate is a gerund (VBG)? E.g. I encountered the sentence
I think it should be nsubj:outer(telling, narcissism) because a local subject of "telling" could be inserted (e.g. "you") or expressed with a possessive ("your").
|
Hm, this would vastly increase the number of But I'm probably the wrong person to be commenting on this, since I don't think of nesting as a type of grammatical function in general. Do you have thoughts on this @manning ? |
We already have |
Just want to point out a beautiful example: "we will have to look at Plan B which would be to put the metering on our ROW" Currently, "which" is the basic subject of "be". It should become the outer subject of "put". But it is a relativizer, so the edep that is changed is E:nsubj(be,B) -> E:nsubj(put,B) ("B" is considered the head of "Plan B"). |
I notice that sometimes the clause-serving-as-predicate is sometimes a coordination. Should the outer subject be propagated as enhanced nsubj:outer for both verbs, or just the first one?
Semantically I don't see a need to say that "sign" is separately a subject of both "drags" and "has", but perhaps we should propagate coordinations irrespective of meaning? |
|
yes, I would expect that regarding "X is to VERB" meaning "X must VERB", I think making 'be' the head would be odd, not just because be is rarely the head but also because it's modal - if "must" is not the head in such constructions, then neither should be be. As for the deprel, I could see doing aux, but then we would have an infinitive governing an nsubj directly without cop, which doesn't explain the morphosyntax well. So maybe cop is actually the more elegant analysis overall. But if you think aux is much better I could go along with that (more faithful to the modality thing, less faithful to the agreement pattern). |
Right, though that also happens with for-to infinitivals. aux seems more straightforward to me than cop. |
I can live with that. Can implement in GUM. |
Fun example with subject-aux inversion: "it was very difficult to see what I would actually look like were I to purchase some of these dresses." |
Implemented in GUM, it's really quite rare though |
@amir-zeldes also
|
Thanks, all fixed, plus some more stuff |
Clause as predicate/:outer subjects (#310)
Update: the main work adding |
The plan is still being finalized. Here are cases with multiple enhanced subjects that need looking at:
The text was updated successfully, but these errors were encountered: