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:

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:

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:

1. The LU's lexicalization home describes the participant category.
2. 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.

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 thirteen namespaces, lemma types or database constraint implementation. Those remain local policies requiring their own validation.