Currently, we set each AND to have the set
ClausalCoordinatePhrase
GroupingCoordinatePhrase
InternalCoordinatePhrase
We will add
LocalCoordinatePhrase
We should be more specific at this point – not introduce alternatives if they are not possible. An example –
Jack and Jill went up the hill.
There is no possibility of any of Clausal or Grouping or Internal on this AND – it can only be Local.
We will define ClausalCoordinatePhrase as joining two clauses, including a partial clause.
Jack fell down and broke his crown, and Jill came tumbling after.
Both ANDs are clausal.
We will define GroupingCoordinatePhrase as jumping to the left over one or more objects, as
The cheeping of birds and the roar of a lion…
The AND is not Local, it groups "roar" with "cheeping". We may not know the precise target, only that it is not the object immediately to the left. If we know the object, the GroupingCoordinatePhrase will provide a right bound.
We will define LocalCoordinatePhrase as active on the object immediately to its left and the base of the object on its right, as
The noise of the birds and honey bees was deafening.
We will define InternalCoordinatePhrase as merging the left object with the right object, as
The red and green car
The long and winding road
The location and time reference data - (the location data is meant)
Internal requires adjectives or multiple nouns in the noun phrase on the right.
We can do a little pruning based on the next object but one in the parse chain, but there will be initial uncertainty among these alternatives, an uncertainty we can reduce at the ParseStalled stage by looking further along the sentence, and then eliminate by creating tentative structure and pruning probabilistically.