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
Instances For
Does the template have an external causer position?
Equations
Instances For
How many grammatically relevant predicates?
Equations
- Semantics.Lexical.Verb.EventStructure.Template.state.predicateCount = 1
- Semantics.Lexical.Verb.EventStructure.Template.activity.predicateCount = 1
- Semantics.Lexical.Verb.EventStructure.Template.achievement.predicateCount = 1
- Semantics.Lexical.Verb.EventStructure.Template.accomplishment.predicateCount = 2
- Semantics.Lexical.Verb.EventStructure.Template.motionContact.predicateCount = 2
Instances For
Predicted aspectual profile for each template.
Equations
- Semantics.Lexical.Verb.EventStructure.Template.state.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.stateProfile
- Semantics.Lexical.Verb.EventStructure.Template.activity.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.activityProfile
- Semantics.Lexical.Verb.EventStructure.Template.achievement.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.achievementProfile
- Semantics.Lexical.Verb.EventStructure.Template.accomplishment.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.accomplishmentProfile
- Semantics.Lexical.Verb.EventStructure.Template.motionContact.toAspectualProfile = Semantics.Tense.Aspect.LexicalAspect.activityProfile
Instances For
Predicted Vendler class for each template (derived from profile).
Equations
Instances For
Templates with complex internal structure — multiple sub-events connected by CAUSE or embedding BECOME — license scopal ambiguities that mono-eventive templates do not.
At the template level, three diagnostics from @cite{dowty-1979} reduce
to two structural properties already defined above:
1. ***again*/*re-* ambiguity** tracks `hasResultState`: templates
embedding [BECOME [STATE]] allow restitutive readings where a
scopal modifier targets just the result sub-event.
2. **Negation over CAUSE** (@cite{koontz-garboden-2009}) tracks
`hasCause`: negation can scope narrowly over CAUSE, denying
the causal link while maintaining the result.
3. **"By itself" licensing** (@cite{koontz-garboden-2009}) also tracks
`hasCause`: "without outside help" requires CAUSE in the meaning.
@cite{krejci-2012}'s insight is that some verbs assigned simpler templates
(eat, wash, dress, learn) nonetheless pass all three diagnostics — evidence
that they have bieventive, causative event structures in their simple forms.
This verb-level property is captured in `RootTypology` and `ArgDerivation`,
not at the template level here.
Does the template embed a result state under BECOME? Templates with [BECOME [STATE]] have a sub-event boundary that scopal modifiers (again, re-, almost) can target independently.
Equations
Instances For
CAUSE implies a result state (accomplishment embeds BECOME).
Causative/Inchoative Alternation #
The accomplishment template [[x ACT] CAUSE [BECOME [y STATE]]]
has an intransitive variant: the achievement [BECOME [x STATE]],
obtained by stripping the external cause. This is the
event-structural core of the causative/inchoative alternation
(@cite{krejci-2012}; @cite{rappaport-hovav-levin-1998}).
Whether the intransitive variant is *monoeventive* (true
anticausative) or *bieventive* (reflexive, with coidentification
of causer and causee) is a language- and verb-specific property
formalized in `MorphologicalCausation.IntransitivizationType`.
The intransitive variant of a template, stripping the external cause. Only accomplishments have an alternation partner.
Equations
Instances For
The intransitive variant retains the result state (BECOME STATE survives stripping of ACT CAUSE).
The intransitive variant loses CAUSE.
Only accomplishments have an intransitive variant (only templates with CAUSE can undergo the alternation).
Predicted subject entailment profile for each template.
Equations
- One or more equations did not get rendered due to their size.
- Semantics.Lexical.Verb.EventStructure.Template.motionContact.subjectProfile = Semantics.Lexical.Verb.EntailmentProfile.sweepBasicSubjectProfile
Instances For
Predicted object entailment profile (if any).
Equations
- One or more equations did not get rendered due to their size.
- Semantics.Lexical.Verb.EventStructure.Template.state.objectProfile = none
- Semantics.Lexical.Verb.EventStructure.Template.activity.objectProfile = none
- Semantics.Lexical.Verb.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.
The fundamental binary distinction in event types: whether a predicate encodes a process (PROC only) or a state change (involves CHANGE).
This crosscuts Vendler's four-way classification: degree achievements are Vendler activities or accomplishments depending on scale boundedness but are event-structurally state-change predicates (@cite{bohnemeyer-2004} §5).
@cite{bohnemeyer-2004} argues this is the primary semantic distinction governing verb classification in Yukatek Maya — more fundamental than Vendler classes for predicting argument linking and transitivization.
Instances For
Equations
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Derive event type from template. Activities and motionContact are processes; states, achievements, and accomplishments involve state change.
Equations
- Semantics.Lexical.Verb.EventStructure.Template.activity.eventType = Semantics.Lexical.Verb.EventStructure.EventType.process
- Semantics.Lexical.Verb.EventStructure.Template.motionContact.eventType = Semantics.Lexical.Verb.EventStructure.EventType.process
- x✝.eventType = Semantics.Lexical.Verb.EventStructure.EventType.stateChange
Instances For
Whether a process is internally caused — the event is instigated by a participant — or externally caused — occurring "spontaneously" without an instigator.
This is a per-verb property of the ROOT, not of the template. Two activity verbs can differ: sing (internal) vs roll (external).
@cite{levin-hovav-1995} §4; @cite{bohnemeyer-2004} §2,6.
- internal : CausationType
- external : CausationType
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
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.