Primitive event structure operators. ACT, CAUSE, BECOME, STATE are from @cite{rappaport-hovav-levin-1998}. MOVE and CONTACT are from @cite{rappaport-hovav-levin-2024}, decomposing manner verbs more finely than the original ACT-based templates.
- ACT : Primitive
- CAUSE : Primitive
- BECOME : Primitive
- STATE : Primitive
- MOVE : Primitive
- CONTACT : Primitive
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- Semantics.Events.EventStructure.instBEqPrimitive.beq x✝ y✝ = (x✝.ctorIdx == y✝.ctorIdx)
Instances For
Canonical event structure templates.
The first four are from @cite{rappaport-hovav-levin-1998}. motionContact is from @cite{rappaport-hovav-levin-2024}
for the sweep/rub/scrape class: [x MOVE y] WHILE [x CONTACT y].
- state : Template
- activity : Template
- achievement : Template
- accomplishment : Template
- motionContact : Template
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- Semantics.Events.EventStructure.instBEqTemplate.beq x✝ y✝ = (x✝.ctorIdx == y✝.ctorIdx)
Instances For
Does the template have an external causer position?
Equations
Instances For
How many grammatically relevant predicates?
Equations
- Semantics.Events.EventStructure.Template.state.predicateCount = 1
- Semantics.Events.EventStructure.Template.activity.predicateCount = 1
- Semantics.Events.EventStructure.Template.achievement.predicateCount = 1
- Semantics.Events.EventStructure.Template.accomplishment.predicateCount = 2
- Semantics.Events.EventStructure.Template.motionContact.predicateCount = 2
Instances For
Predicted aspectual profile for each template.
Equations
- Semantics.Events.EventStructure.Template.state.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.stateProfile
- Semantics.Events.EventStructure.Template.activity.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.activityProfile
- Semantics.Events.EventStructure.Template.achievement.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.achievementProfile
- Semantics.Events.EventStructure.Template.accomplishment.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.accomplishmentProfile
- Semantics.Events.EventStructure.Template.motionContact.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.activityProfile
Instances For
Predicted Vendler class for each template (derived from profile).
Equations
Instances For
Predicted subject entailment profile for each template.
Equations
- One or more equations did not get rendered due to their size.
- Semantics.Events.EventStructure.Template.motionContact.subjectProfile = Semantics.Events.ProtoRoles.sweepBasicSubjectProfile
Instances For
Predicted object entailment profile (if any).
Equations
- One or more equations did not get rendered due to their size.
- Semantics.Events.EventStructure.Template.state.objectProfile = none
- Semantics.Events.EventStructure.Template.activity.objectProfile = none
- Semantics.Events.EventStructure.Template.achievement.objectProfile = none
Instances For
Accomplishment subject is a full agent (5 P-Agent entailments).
motionContact subject has the same profile as basic sweep (movement + IE, underspecified for agentivity).
For motionContact verbs, which sub-predicate determines argument realization (@cite{rappaport-hovav-levin-2024} §3.3–3.4).
- motion : DeterminingPredicate
- contact : DeterminingPredicate
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
When CONTACT determines argument realization, the subject is an effector (movement + IE → external argument). This yields the simple transitive frame: "The wind swept the deck".
The motionContact object profile exists and is a force recipient.
Instrument lexicalization adds agentivity to a template by restricting the moving entity to a specific instrument, forcing volition + sentience
- causation. The result is the broom-sweep subject profile.
Equations
Instances For
Instrument lexicalization strictly increases agentivity for motionContact templates (@cite{rappaport-hovav-levin-2024} §3.5: broom-sweep is more agentive than basic sweep).
Lexicalized motionContact has full proto-agent profile (5 entailments).
Levin classes map to event structure templates via meaning components. The core correspondence (@cite{rappaport-hovav-levin-1998} §3; @cite{rappaport-hovav-levin-2010} §2):
| Meaning component pattern | Template | Example class |
|---|---|---|
| CoS + causation | accomplishment | break (45.1), destroy (44) |
| CoS, no causation | achievement | appear (48.1), calve (28) |
| No CoS, no motion | state | exist (47.1), admire (31.2) |
| Otherwise | activity | hit (18.1), run (51.3) |
The `motionContact` template is specific to the sweep/rub/scrape
class and requires a class-specific override.
Predicted event structure template from meaning components.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Predicted template for a Levin class, with class-specific overrides.
Equations
Instances For
Verification: canonical quadruple #
Break → accomplishment (CoS + causation → [ACT CAUSE BECOME]).
Hit → activity (contact + motion, no CoS → [ACT]).
Touch → activity (contact only, no CoS).
Cut → accomplishment (CoS + causation).
Change-of-state classes → accomplishment #
All §45 CoS classes map to accomplishment.
Motion classes → activity #
Motion verbs are activities (no CoS, have motion).
Stative classes → state #
Perception/psych statives map to state template.
Achievement classes #
Appear (CoS without causation) → achievement.
Calve (CoS without causation) → achievement.
Special: motionContact #
Wipe class → motionContact (class-specific override).
Template → aspectual class consistency #
Accomplishment classes (break, cut) are predicted telic.
Activity classes (hit, run) are predicted atelic.
State classes (exist, admire) are predicted stative.