home edit page issue tracker

This page pertains to UD version 2.

nmod:desc: descriptor modifier in nominal

** IMPLEMENTATION IN PROGRESS **

This relation subtype applies to nominal modifiers that we term descriptors. These are bare nominals that occur in or with a name, and are not prepositional/possessive or part of the English compound construction. For personal names, titles and role descriptions are a prime example. Business names may include descriptors like Inc. Semantically, a descriptor assigns a referent to a class or may disambiguate the referent where the main part of a proper name is not a sufficiently unique identifier. Crucially, omitting the descriptor does not affect the grammaticality of the expression (and does not come across as an abbreviation of the full name).

Descriptors are bare modifiers (i.e. the descriptor noun lacks a determiner, possessive, or numeral). This distinguishes them from appositives: the appos relation holds between two full nominals. In principle, descriptors are a special case of nmod:unmarked.

Personal Names

One descriptor construction is the pre- or postmodification of a personal name with a (bare nominal) role or title:

** NOTE: we need to standardize UPOS. SYM says that Dr. and Mr. are NOUN but in English treebanks they are predominantly PROPN. **

A descriptor must be omissible, but not all omissible parts of a name are descriptors: if the main part of a name has multiple parts such that there are at least two plausible heads, flat is the appropriate choice, as is the case with the main parts of a personal name.

Non-numeric generational suffixes are also nmod:desc (but see Numbered Entities below):

Business Names

Corporate suffixes like Inc., Corp., and LLC (as well as their non-abbreviated forms) are considered optional descriptors as they are often omitted from the name of the company. Regardless of etymology, they are tagged PROPN.

Complex Dates and Addresses

These are considered to have time or place modifiers, and thus fall under nmod:unmarked.

Idiosyncratic Name Patterns Analyzed as Flat Expressions

In addition to the main parts of a personal name, further name patterns analyzed with flat rather than a headed construction are given below. Note that the morphosyntax of name patterns differs by language, with some exhibiting agreement (as a sign of head or modifier status) where it is lacking in English, so a flat analysis of an English expression may not hold for its translation into another language.

Numbered Entities

When the name of a category combines with a (pseudo)number to form a name, and the number is serving as an identifier rather than as a quantifier, we use flat:1

The “number X” construction also serves to clarify that a number is serving as an identifier; “number X” forms a flat expression that can be combined within a larger flat expression:

A product name that includes a model or version number is considered a flat expression:

For simplicity, regnal/generational number suffixes are considered part of flat expressions just like version numbers, though they semantically resemble Jr. and Sr.:

Toponyms

We also use flat for toponyms where the noun representing the entity type comes first. This word order is anomalous relative to other English constructions such that tests for headedness are inconclusive:

By contrast, if the identificational part of the toponym precedes the entity type, this is analyzed as a regular right-headed compound dependency:

  1. This is a departure from a guideline articulated previously: according to de Marneffe et al. (2021), p. 285, the (pseudo)number attaches as nmod, though the main point of that passage is to articulate why nummod is not appropriate (no rationale for headedness is presented). 


nmod:desc in other languages: [en]
BESbswyBESbswyBESbswyBESbswy