Correct semantics for proper noun constructions in the ERG?

Onto my next dataset :slight_smile: and there are a LOT of proper nouns.

I have questions about what the appropriate constructions are for a number of examples.

  • Firstname Lastname (e.g. “Liz Conrad”) – is this a compound construction with the last name as the head noun?
    • What about if there are three names? How does it get broken up? Does it depend on if the person has “two last names” vs. a middle name and a last name?
    • Either way will “work” I’m sure but I’m curious what the “correct” analysis would be
  • Seattle, Washington – I thought this could be a compound too, but I have the feeling that “Seattle” should be the head noun and in a regular compound I think the second one is always the head(?)
  • German Language – compound, or adjective+noun?
  • Seattle Airport – would the “airport” in this compound be just the normal noun “airport” or is it treated differently when it’s in a proper noun?
  • The National Hockey League – similar to above, this phrase can be built out of “regular” words, but combined they form a proper noun, is there a special treatment of this as far as semantics go? Or would it just be a compound of ‘hockey+league’ with the adjective ‘national’ in front?
1 Like

I’m curious about the last cases a bit — for @ecconrad ‘s purposes, it seems like saying that League and Airport are proper nouns is the easier path to broad coverage (likewise for German in German language) since named_rel is one place where we can handle unknown entries in generation.

So what is the potential advantage of using the common noun league or airport (or the adjective German) in such cases? Maybe eventually better realization ranking support, with a WordNet-connected ERG?

Proper noun constructions deserve their own little monograph, for both their syntax and their semantics. Here are some remarks on the types you’ve asked about:

(1) Firstname Lastname - Yes, the current analysis treats this as a compound noun with the second element being the head. If there are three names, there is the expected ambiguity, where the bracketing can be either [[Mary Jane] Smith] or [Mary [[Smith Jones]]. The decision to make the second element the head is probably wrong, given the behavior in coordinated names such as “John and Mary Smith” where the resulting NP is plural, not singular, which would follow if the first element were the head. Note also that we should probably block “John Smith and Jones” meaning the coordination of “John Smith and John Jones”, which would be a little easier to do if the compound were left-headed. Perhaps we can have a discussion on the merits of such a change at the summit this summer, before I implement it, since it would have a marked effect on the external interface to the grammar.

(2) Cityname, Statename (and Cityname, Countryname) - Yes, I agree that here too the first element should be the head, not the second one, again motivated by coordination/agreement examples, where “Paris and Lyons, France” is good and should be plural, while “Berlin, Ohio and Germany” should be blocked with the meaning “Berlin, Ohio and Berlin, Germany”.

(3) German Language - The capitalization of “Language’“ here is dubious in my view, since we still have to say “we speak the German language” not “we speak German Language”, treating “language” as a count noun, different from “language” used as a mass noun as in “We should use legal language here”. The word “German” in this expression signifies, I think, the name of the language and hence is a proper noun, so “German language” is a compound noun with the second element a common noun, where we can paraphrase “We speak the German language” with “We speak German”. This is probably different from the use of “German” as an adjective as in “We visited a German city”; note that we contrast “They speak a Germanic language” with the less felicitous “They speak a German language”. This adjective vs. noun contrast is clearer where the name of the country or culture and the name of the language differ, as in “The English language is spoken here”, not “The American language is spoken here” (and of course normally not “American is spoken here”). Further, in “the Australian English dialect” the structure should have the adjective “Australian” modifying the proper noun “English” with “Australian English” forming an NP-N compound for “Australian English dialect”. It would be awkward if English here were an adjective, since [[Adj Adj] N] would force the first adjective to modify the second, or else both adjectives would separately have to modify the noun, not the intended interpretation.

(4) Seattle Airport - These so-called post-title constructions are a little more vexing, since the capitalization of the second element seems to matter, and capitalization is not so consistent. I’m not sure “Seattle Airport” is the clearest example of this type, since it sounds odd to say “We arrived at Seattle Airport” instead of “We arrived at the Seattle airport” (or maybe “We arrived at the Seattle Airport”). So let’s use “Seatac Airport” instead. If the usage is “We arrived at Seatac Airport” (with capitalized “Airport”) I think we still want to treat it as a common noun serving as a post modifier of the head “Seatac”, not as a compound noun (which would be odd in having a singular count noun heading an NP missing its determiner). So this is treated with a special construction in the ERG, making the first daughter the head. (Maybe if we switched to treating “Mary Smith” with “Mary” as the head, we could find a single left-headed construction analysis for both.) In contrast, if the sentence is “We arrived at the Seatac airport” with an overt determiner, the ERG treats “Seatac airport” as an ordinary NP-N compound with “airport” as the head, consistent with the fact that we don’t usually get an overt determiner with compound names: “*We met the Mary Smith today”. Note that the ERG offers another analysis of “Seatac Airport” just like “Mary Smith” where “Airport” is a proper noun that has nothing in common semantically with the common noun “airport”, but when annotating the ERG treebanks, we deprecate these semantically opaque analyses.

(5) “The National Hockey League” - These are the most vexing types of constructions, where there is a multi-token expression for a named entity where it is tempting to try to analyze it compositionally rather than as a semantically opaque sequence of proper nouns. When the named entity has an overt determiner as in your example, we normally choose the analysis where the final word is a common noun and the head of the compound noun phrase (even though “League” is capitalized) to account for the overt determiner. Note that we normally see lowercase for “the” if it’s not sentence-initial: “We complained to the National Hockey League”, not “… to The National…”. But it seems like a road toward madness to try to consistently analyze the other elements of multi-word named entities as ordinary adjectives and nouns to produce a transparently compositional compound structure, since people inventing names don’t always combine the elements in conventional ways.
To summarize a little for these last two types, if there is no overt determiner in the named expression and the last element can be treated as a common noun (capitalized or not), then we treat that last element as a modifier of the compound proper name preceding it (so “George Washiington University” will have “university” as a modifier of the name-name compound “George Washington”). If there is an overt determiner, then the last element is still treated is a common noun, but now it is the head of a compound NP-N phrase so we can account for the presence of that determiner, as in “The National Hockey League”. Finally, for an expression such as “The New York Stock Exchange” we have settled on ignoring the capitalization of “Stock” and “Exchange”, treating “stock exchange” as a multi-word common noun which heads the full NP, with “New York” as a multi-word proper noun that forms an NP-N compound with “stock exchange”. As you can see, this is not the only obvious analysis possible, but offers a pretty good balance among consistent annotation, robustness, syntactic normality, and semantic transparency, even though it achieves none of those perfectly.

1 Like

Thanks for your detailed response :slight_smile:

As far as “the Seatac Airport” and “the National Hockey League” what does the MRS look like when there’s a noun modifying the preceding compound noun?

Relatedly, is there an MRS that is underspecified between the overt/no overt determiner analyses?

I ask since in my case I’m building up the MRSs from “scratch” and then passing them off to the ERG for generation and I’m using the “def_udef_a_q” for everything, delegating better quantifier selection to future work.

By “noun modifying the preceding compound noun” I assume you mean examples such as “the three-runway Seatac Airport” or “the legacy National Hockey League”. These sound best with the overt determiner, so “airport” and “league” will each be a common noun that heads the compound noun phrase “Seatac Airport” and “[National Hockey] League”, where the leftmost modifying noun combines with the compound noun phrase to form a larger compound noun, adding another compound_rel with its two arguments being the ARG0 of “_legacy_n” and the ARG0 of “_league_n”, or the ARG0 of “_runway_n” and the ARG0 of “_airport_n”.

Underspecification over the presence or absence of the determiner isn’t currently possible, alas. For generation purposes you might well ignore the “post-title” analysis of nominal phrases like “Seatac Airport” and always treat capitalized “Airport” as a proper noun to produce a name-name compound. But as noted in a related thread, the underspecified predicate def_udef_a_q does not subsume proper_q, so the input MRS will already have to dictate whether the determiner is implicit (proper_q) or overt (the_q).

What I was referring to was this:

What does the MRS look like when we treat “airport” as a common noun modifying “Seatac”? Since you said it’s not treated as a compound I’m wondering what the MRS should look like.

I’m also confused because, as an example from the dataset I’m using, “Aarhus Airport” is one of the strings. In this case, it feels odd that the head would be “Aarhus,” since when saying “Aarhus Airport” one is talking about the airport, not the city. Is Seatac different because “Seatac” alone can specifically refer to the airport?

In the case of “Aarhus Airport” I notice that when parsing I get both an MRS where “Aarhus” is the ARG1 of the compound and one where “airport” is the ARG1 of the compound and I’m not sure what to make of this:

compound.ARG1 = Aarhus.ARG0 (surprising)
[ TOP: h0
  INDEX: e2 [ e SF: prop ]
  RELS: < [ unknown<0:14> LBL: h1 ARG: x4 [ x PERS: 3 NUM: sg IND: + ] ARG0: e2 ]
          [ proper_q<0:14> LBL: h5 ARG0: x4 RSTR: h6 BODY: h7 ]
          [ named<0:6> LBL: h8 ARG0: x4 CARG: "Aarhus" ]
          [ _airport_n_1<7:14> LBL: h10 ARG0: x11 [ x PERS: 3 NUM: sg IND: + ] ]
          [ udef_q<7:14> LBL: h12 ARG0: x11 RSTR: h13 BODY: h14 ]
          [ compound<7:14> LBL: h8 ARG0: i15 ARG1: x4 ARG2: x11 ] >
  HCONS: < h0 qeq h1 h6 qeq h8 h13 qeq h10 > ]

Generating from the above MRS: 
Aarhus Airport
Aarhus Airport.
Aarhus, Airport
Aarhus, Airport.


compound.ARG1 = airport.ARG0 (what I normally expect)
[ TOP: h0
  INDEX: e2 [ e SF: prop ]
  RELS: < [ unknown<0:14> LBL: h1 ARG: x4 [ x PERS: 3 NUM: sg IND: + ] ARG0: e2 ]
          [ udef_q<0:14> LBL: h5 ARG0: x4 RSTR: h6 BODY: h7 ]
          [ compound<0:14> LBL: h8 ARG0: e9 [ e SF: prop TENSE: untensed MOOD: indicative PROG: - PERF: - ] ARG1: x4 ARG2: x10 [ x PERS: 3 NUM: sg IND: + ] ]
          [ proper_q<0:6> LBL: h11 ARG0: x10 RSTR: h12 BODY: h13 ]
          [ named<0:6> LBL: h14 ARG0: x10 CARG: "Aarhus" ]
          [ _airport_n_1<7:14> LBL: h8 ARG0: x4 ] >
  HCONS: < h0 qeq h1 h6 qeq h8 h12 qeq h14 > ]

Generating from the above MRS: 
Aarhus, airport.
Aarhus, airport
Aarhus airport
Aarhus airport.

I suppose I find this behavior surprising because up until now I always expected the ARG1 of the compound relation to be the the right element in the string. So I’m surprised to find (1) both of these MRSs in the first place and (2) that they generate the same strings and neither of them generate the (admittedly undesirable) “airport Aarhus”

There are two analyses for the fragment “Aarhus airport”, (1) a full NP fragment where “Aarhus” is the head and “airport” is a modifier, and (2) a compound noun fragment (still lacking a determiner) where “airport” is the head. In both analyses, the ARG0’s of the two nouns are related by a compound_rel whose ARG1 is the head of the phrase, so in (1) the ARG0 of “Aarhus” is the ARG1, while in (2) the ARG0 of “airport” is the head. You’re right that most of the time the head of a compound phrase is the right daughter, but for these “post-title” constructions like "Madison Avenue” or “Waikiki beach”, it is atypically the left daughter (the proper noun) which is the head. We decided to retain the use of the “compound” relation for this atypical ordering of the two daughters in such phrases because there are instances where the non-head common noun can also precede the proper noun: consider “Lake Michigan” vs. “Crater Lake”, or “Fort Sumter” vs. “Beverly Fort”. Most of these modifier nouns have a strong preference about either following the head (like “airport” or “avenue”) or preceding the head (like “doctor” in “Doctor Smith”or “number” in “number seven”), but since come can appear either before or after, we wanted to keep the MRS the same. Perhaps we should reconsider this decision, and introduce a separate relation for the post-head modifier ones, so that your expectation about the ARG1 of the compound_rel always being the head would be preserved.

Note that for both “Seatac Airport has several runways” and “Aarhus Airport has one runway” it is the first daughter in the compound that names the thing being referred to: we can also say “Seatac has several runways” and “Aarhus has one runway”, in both cases referring to the airport. Adding the post-head modifier disambiguates the reference for “Aarhus” since it could refer either to the city or to the airport that bears the same name.

Hi,

I am not sure I find the final argument convincing. We can also say ‘This airport has several runways’ and think of Seatac as disambiguating it, … But the argument that Bond is the head of Mister Bond is more convincing, and then it makes sense to treat them the same way. Do you know what Huddleston and Pullum say about these? I can look tomorrow, …

Getting back around to working on constructions like these.

By default, my system doesn’t impose any number information so I usually expect both singular and plural results, but for some reason I’m getting only plural results for proper nouns in compounds:

[ TOP: h22
  INDEX: e19
  RELS: < [ unknown LBL: h18 ARG: x1 ARG0: e19 ]
          [ def_udef_a_q LBL: h17 ARG0: x1 RSTR: h15 BODY: h16 ]
          [ compound LBL: h13 ARG0: e10 [ e PROG: - ] ARG1: x1 ARG2: x3 ]
          [ udef_q LBL: h8 ARG0: x3 RSTR: h6 BODY: h7 ]
          [ named LBL: h4 ARG0: x3 CARG: "Aarhus" ]
          [ _airport_n_1 LBL: h13 ARG0: x1 ] >
  HCONS: < h6 qeq h4 h15 qeq h13 h22 qeq h18 > ]

The Aarhusses airport
The Aarhusses, airports.
The Aarhusses airports.
An Aarhusses airport
A Aarhusses, airport
A Aarhusses, airport.
Aarhusses, airports
Aarhusses, airport
.....

It seems if I change the quantifier on the proper noun to be proper_q then it doesn’t happen anymore. The udef_q quantifier probably isn’t appropriate and I plan to update it in my next round of experiments (I asked about quantifying proper nouns here). But regardless, why is it that using udef_q causes the proper noun to be realized exclusively as plural?