FrameNet Patterns and FNBr Policy
This page distinguishes Berkeley FrameNet guidance from FNBr policy. The sources inform semantic review; they do not authorize automatic frame creation, LU movement or merging.
Frame coherence#
FrameNet II, §§2.1.1–2.1.3, pp. 12–13, requires coherent essential participant structure, aspectual entailments and perspective across a frame's LUs.
- Count conceptually present participants, including null instantiation, not just overt arguments.
- Causatives and inchoatives generally require different frames because the causing participant/subevent changes the semantic structure.
- Passive and productive middle constructions can suppress realization without removing a participant from the lexical meaning. They do not automatically require a different frame.
- Different entailed stages or transitions support frame separation. An attempted or ongoing action is not interchangeable with a successfully completed one.
- Shared words or glosses do not establish equivalent readings. A mixed-reading LU requires partitioning evidence before consolidation.
Causative/inchoative/state families#
Section 6.1.6, p. 85, describes Causative_of and Inchoative_of as close, non-inheritance relationships among causing, changing and holding-state frames. It gives this inheritance guidance:
| Family member | Inheritance anchor |
|---|---|
| Causative | Transitive_action |
| Inchoative | Event |
| State | State or Gradable_attribute |
Check paths and FE mappings, not just direct edges. A missing path is a review candidate; deciding which relation or frame is missing requires semantic evidence. A State/Gradable_attribute inheritance anchor does not automatically select the FNBr State namespace: namespace and FrameNet inheritance are different classifications.
Frame relations, FE correspondences and LU-level lexical relations are separate structures. One does not prove the presence of another. Verify stored endpoints and direction before proposing edits.
Neutral frames and perspectives#
Sections 2.1.3 and 6.1.2, pp. 13 and 82–83, describe Perspective_on between a neutral scene and its perspectivized frames. Neutral frames are normally non-lexical and non-perspectivized; they generally support at least two viewpoints, with exceptions explicitly recognized by the book.
Do not turn that generalization into a fixed child-count requirement. Compare the meanings of the alternatives and their FE mappings. A neutral frame does not inherit its namespace from one viewpoint, and two frames sharing a namespace need not be perspectives of one another.
FNBr's stored direction must be read from the relation metadata. In the structural audit, the Perspective relation is stored neutral → viewpoint (direct label “Is perspectivized in”); this must not be confused with the English label “Perspective on.”
Events and their conditions#
Section 6.1.1, item 6, p. 82, connects Event with Event_initial_state and Event_endstate through Precedes. Section 6.1.5, p. 84, defines Precedes in the context of subframes of a complex frame.
FNBr's EventState review pattern asks whether an occurrence and its preceding/resulting conditions are distinguished appropriately. It is a local review label, not a relation named EventState established by this book. A participial form may have eventive and condition readings; review them separately. Do not create every possible state frame mechanically or infer a new relation from the label.
CoreSet, Requires and Excludes#
Sections 3.2.2.1–3.2.2.3, pp. 25–27, define distinct FE constraints:
| Device | Meaning |
|---|---|
| CoreSet | Any member can satisfy a semantic valence; several may co-occur. Source, Path and Goal are the book's example. |
| Requires | Realization of one FE requires another in the relevant construction. |
| Excludes | Alternatives cannot be realized together as direct dependents on the same annotation layer; nested layers can contain both. |
Excludes is not a synonym for CoreSet and does not require separate perspective frames for each alternative. Section 2.1.1.2 uses Excludes to preserve different FE types, including metonymically related complements, within a frame. Section 6.1.1 explains that a child may inherit all alternatives or an appropriate subset.
Do not impose global Experiencer/Cognizer or Agent/Cause Excludes groups from namespace membership. A proposed group needs evidence from the particular frame and its annotation structure.
Agentive names and participant associations#
Sections 6.2.3.4–6.2.3.4.3, pp. 90–91, describe Berkeley's biframal LU treatment. An Agentive noun such as murderer can be listed in an event frame while virtually inheriting from People; Participating entity covers other participant-denoting LUs. The book identifies FE mismatches as a cost of this resource-saving treatment.
FNBr policy: agentive names evoke Entity frames, not the associated activity frame merely because they denote its Agent. This is a local representation policy, not a claim that Berkeley forbids biframal LUs.
Keep two facts separate:
- The LU's lexicalization home describes the participant category.
- An association connects that participant reading to the appropriate FE of the event or relation.
Use an FE–Frame association only when all relevant LUs of the Entity frame are suitable for the intended FE contribution. Otherwise use LU–FE associations for the qualifying subset. Do not move or merge LUs without checking the receiving frame's definition, participant inventory and annotation mappings.
Constraints can be nested through CON nodes. Resolve the full expression and its operators before concluding that an association is missing; absence of a direct FE endpoint is insufficient. A frame-level association cannot stand for a selectively suitable subset.
Qualities and their attribution#
Berkeley FrameNet lists a quality noun in the same frame as the predicates that ascribe its values: beauty.n with beautiful.a in Aesthetics, fear.n with afraid.a in Fear, depravity.n with wicked.a in Morality_evaluation. The noun names the frame's Attribute, incorporated in the LU, while the adjectives name a Value.
FNBr policy (decided 2026-11-12): naming a quality itself and ascribing a value of it to a bearer are two lexicalization homes, in the same way that naming a participant and describing the event are.
| Participants | Qualities | |
|---|---|---|
| What is named | a participant category (trabalhador) | a quality, an aspect inhering in a bearer (moralidade, homossexualidade) |
| Its home | an Entity frame | a frame in the Quality namespace, under the non-lexical Quality frame |
| The predicating side | the event frame (trabalhar) | a frame under Attributes that ascribes a value (moral, homossexual) |
| DUL grounding | Object / Role, participating in an Event | Quality, taking a Region |
| The link between the two | an LU–FE or FE–Frame association to the event FE | the quality frame corresponds to the Attribute FE of the attribute frame |
Keep two facts separate, as for agentive names:
- The lexicalization home of the quality noun is the frame that names the quality (Morality, Sexuality).
- The correspondence between that frame and the frames that ascribe its values (Morality_evaluation, Sexual_orientation_descriptor) is a relation between frames, not a reason to put the noun beside the adjectives. It is recorded between the anchors (Attributes uses Quality); the frame-to-frame pairs are not yet recorded.
As Entity is apart from the eventive namespaces, Quality is a namespace apart from the Attribute family (2026-11-12). The two anchor frames are linked by Using: Attributes uses Quality, with Quality.Quality filling Attributes.Attribute, so every frame that ascribes a value points, through its parent, at the quality whose value it ascribes. See Quality. See Attribute: Quality frames and LU Allocation Rules, R11.
Scope. The pattern has been applied to Morality and Sexuality. Most quality nouns still share frames with their value predicates: about 2,400 LUs, mainly in State (health conditions), the Gradable namespace and Experiencer_state (emotion nouns such as medo). Two boundaries were decided on 2026-11-12:
- Emotions and cognition stay Experiential: the psychological gate comes first, as Berkeley keeps fear.n in Fear.
- Health conditions stay State. All the health-condition frames keep their namespace; whether some conditions are qualities is left to a later review of the Health domain model..
As with agentive names, applying the pattern further is a targeted evaluation that produces a review list, not automatic moves (Lemmas §8). A frame mixing quality nouns and value predicates is reviewed reading by reading. The lemma type is a cue to which nouns to review, never the verdict.
Source#
Ruppenhofer, Josef; Ellsworth, Michael; Petruck, Miriam R. L.; Johnson, Christopher R.; Baker, Collin F.; Scheffczyk, Jan. FrameNet II: Extended Theory and Practice, revised November 1, 2016 (Release 1.7).
The cited passages were checked in the supplied local PDF, 2016-FrameNet_II_Extended_theory_and_practice.pdf. Page numbers above are printed page numbers. Official distribution.
The book does not prescribe FNBr's twenty-five namespaces, lemma types or database constraint implementation. Those remain local policies requiring their own validation.