You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So loc is a kind of supertype for _in_p_state... but still, we read location, right? Here the preposition in is more about with or X has the shape ....
Maybe this WordNet definition should be best written as one of the following paraphrases.
a charge with the shape of a small ring
a charge that has the shape of a small ring
Does it make sense? I mean, it is to expect so much from ERG to give us all our desired interpretations for a poorly chosen NL sentence.
(This is all thoughts from a non native English speaker)
The text was updated successfully, but these errors were encountered:
I think "in" is a perfectly good choice of preposition in this sentence.
I suppose this comes down to how we are supposed to interpret _in_p_loc. If this just means "non-temporal" (because it contrasts with _in_p_temp), then this seems okay: "in the shape of" means something spatial, not temporal.
But still, no reason for not having a reading with _in_p_state, right?
Although, _in_p_state is actually a subtype of _in_p_loc ... so maybe that is the reason, no deep constraint from the noun to more fine-grained interpretation of the preposition.
http://delph-in.github.io/delphin-viz/demo/#input=a%20charge%20in%20the%20shape%20of%20a%20small%20ring&count=10&grammar=erg2018-uw&mrs=true&dmrs=true
Why I didn't get a reading with
_in_p_state
? OK, from the ERG source, I know that.So loc is a kind of supertype for _in_p_state... but still, we read location, right? Here the preposition
in
is more aboutwith
orX has the shape ...
.Maybe this WordNet definition should be best written as one of the following paraphrases.
Does it make sense? I mean, it is to expect so much from ERG to give us all our desired interpretations for a poorly chosen NL sentence.
(This is all thoughts from a non native English speaker)
The text was updated successfully, but these errors were encountered: