Entity Namespace

Core definition#

Entity frames profile a kind of entity or participant: people, artifacts, organisms, substances, places, organizations, information objects and other referents. They describe what something is, rather than an action, a property dimension or a connection considered as such.

ENTITY(Referent, [Category])

Nouns are common lexicalizations but POS is not the membership test. Entity meanings can be used referentially (o médico chegou) or predicatively (João é médico). Nominal predication does not itself make the frame Relation or Attribute.

Scope and contrasts#

Meaning Guidance
Person category: médico, trabalhador Entity when the participant category is the lexical contribution
Artifact/substance: recipiente, água Entity
Place or organization: cidade, empresa Entity
Document or social object: contrato, lei Entity on the referent-denoting reading, not automatically every reading
A period named as a referent: semana Entity; distinguish relating an event to a time
Working, constructing or arriving An event meaning, not Entity simply because a nominal form can refer to it
Height, colour, a property value Attribute family (Gradable, Classifying) or the appropriate condition/psychological category
A quality named as such: moralidade, homossexualidade Quality namespace; a doctrine or field (budismo, filosofia) stays Entity under Abstract_entity
Possession or kinship connection Association (Relation family) when the connection itself is profiled

A role noun can depend on an event or another participant while still naming an entity category. External dependence at the lemma-type layer does not prohibit an Entity-frame allocation. Conversely, not every relational noun is automatically routed here: review its particular reading and frame definition.

Agentive names: FNBr policy#

Agentive names evoke Entity frames. Trabalhador naming a person is not allocated to a work event merely because the person fills its Agent/Worker FE.

Record the event participation separately:

  • Use an FE–Frame association only when all relevant LUs of the Entity frame are suitable fillers for the intended contribution.
  • Otherwise use LU–FE associations for the qualifying readings.
  • Inspect nested constraint expressions before reporting an association absent.

This preserves the participant category's own annotation needs while connecting it to the event. It differs from Berkeley's biframal Agentive noun workaround; see FrameNet patterns.

Characteristic signature#

A general Entity frame profiles the referent through an Entity FE. More specific frames may add person-, artifact- or domain-specific FEs; one core referent does not mean every Entity frame must have exactly one FE.

Reality, natural/artifactual constitution and physical/social/representational character are useful organizing distinctions. They are not mandatory binary tests or proof that every corresponding inheritance edge exists.

Lemma types and constructions#

Entity frames are commonly evoked by object and role lemmas, and some by value lemmas (americano naming a person by origin), but lemma types do not restrict allocation (Lemmas §8). There is no separate .entity lemma type.

Substantivized adjectives can refer to an entity without changing their lemma type. Distinguish productive ellipsis from a lexicalized participant noun using meaning and POS/lemma identity. A compatible type does not establish that a particular Entity frame is the correct destination.

Review diagnostics#

Ask what the lexical anchor names: a participant category, a property, a relation or an event? Inspect incorporated FEs and annotations. Do not classify from nominal form, definiteness, countability or the predicate surrounding the target.

Preserve distinctions between entity naming and relational predication, including when the same lemma has readings in both categories. Defer unclear role/entity boundaries rather than changing an entire lemma's allocations together.