Verb-Root-Outcomes: Reversal and Restitution #
@cite{bhadra-2024}
Bhadra, D. (2024). Verb roots encode outcomes: argument structure and lexical semantics of reversal and restitution. Linguistics and Philosophy 47: 557–610.
Core contribution #
Every verb root is lexically equipped with a set of outcomes — the possible states of the direct object after the verb's force is applied. The cardinality of this set determines compatibility with the reversative prefix un- and the restitutive prefix re-:
- PFC (potential-for-change): multi-membered outcome sets (fold, wrap, coil) → compatible with both un- and re-
- IE (impingement-effecting): singleton outcomes, surface only (hit, scrub) → incompatible with both
- COS (change-of-state): singleton outcomes, integral change (break, destroy) → incompatible with un-, partially compatible with re-
Boundary state operators #
res(e)(x) and pre(e)(x) yield the state of object x at the right and
left boundaries of event e. These are NOT temporal operators — they yield
property bundles (lifespan points). Reversative un- requires inverse
equivalence of boundary states across events; restitutive re- requires
result-state equivalence.
Bridges #
ForceTransmissionClassrefinesAffectednessDegree.potentialinto PFC vs IELevinClass.forceTransmissionClassbridges @cite{levin-1993} classes to @cite{bhadra-2024}RootType.resultroots have singleton outcomes;RootType.propertyConceptis orthogonalTemplate.hasResultStateis necessary but not sufficient for un-/re- (must also check outcome cardinality)
Cardinality of a verb root's outcome set — the possible states of the object after force transmission.
multi-membered sets (PFC) > singleton sets (IE, COS) > empty sets
- multi : OutcomeCardinality
- singleton : OutcomeCardinality
- empty : OutcomeCardinality
Instances For
Equations
Equations
- instBEqOutcomeCardinality.beq x✝ y✝ = (x✝.ctorIdx == y✝.ctorIdx)
Instances For
Equations
- One or more equations did not get rendered due to their size.
- instReprOutcomeCardinality.repr OutcomeCardinality.multi prec✝ = Repr.addAppParen (Std.Format.nest (if prec✝ ≥ 1024 then 1 else 2) (Std.Format.text "OutcomeCardinality.multi")).group prec✝
- instReprOutcomeCardinality.repr OutcomeCardinality.empty prec✝ = Repr.addAppParen (Std.Format.nest (if prec✝ ≥ 1024 then 1 else 2) (Std.Format.text "OutcomeCardinality.empty")).group prec✝
Instances For
Equations
- instReprOutcomeCardinality = { reprPrec := instReprOutcomeCardinality.repr }
Classification of force-transmitting verbs by impact type.
Table 1: the three classes are distinguished by whether force transmission occurs, whether integral change is entailed, and whether surface impingement is effected.
| Class | Force | Integral change | Impingement |
|---|---|---|---|
| PFC | ✓ | not entailed | ✗ |
| IE | ✓ | not entailed | ✓ |
| COS | ✓ | entailed | ✓/✗ |
This refines AffectednessDegree.potential (which lumps PFC and IE).
- potentialForChange : ForceTransmissionClass
- impingementEffecting : ForceTransmissionClass
- integralChange : ForceTransmissionClass
- noForceTransmission : ForceTransmissionClass
Instances For
Equations
- instBEqForceTransmissionClass.beq x✝ y✝ = (x✝.ctorIdx == y✝.ctorIdx)
Instances For
Equations
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Outcome set cardinality for each force transmission class.
PFC verbs have multi-membered sets because their actions produce one of many possible discrete outcome states (slightly bent, halfway bent, etc.). COS and IE verbs have singleton sets (specific result). No-force verbs have empty sets (no object-state change).
Equations
- ForceTransmissionClass.potentialForChange.outcomeCardinality = OutcomeCardinality.multi
- ForceTransmissionClass.impingementEffecting.outcomeCardinality = OutcomeCardinality.singleton
- ForceTransmissionClass.integralChange.outcomeCardinality = OutcomeCardinality.singleton
- ForceTransmissionClass.noForceTransmission.outcomeCardinality = OutcomeCardinality.empty
Instances For
Boundary states of an event's impact on an object.
pre = state at left boundary (pre-state, eq. 65)
res = state at right boundary (result state, eq. 64)
These are NOT temporal operators — they yield property bundles (lifespan points) at event boundaries, enabling equivalence comparisons across events.
- pre : S
State of the object at the left boundary of the event
- res : S
State of the object at the right boundary of the event
Instances For
Reversibility condition (eq. 49): the result state of the base event equals the pre-state of the affixed event, and vice versa.
Captures the "inverseness" at the heart of un-.
Instances For
Restitution condition (eq. 50): the result state of the affixed event equals the result state of the base event.
Captures the "same result achieved again" at the heart of re-.
Equations
- restitutive base affixed = (affixed.res == base.res)
Instances For
un- compatibility (eq. 67): requires multi-membered outcome set (reversibility) AND the possibility of inverse equivalence between boundary states. Only PFC verbs satisfy both conditions.
Instances For
re- compatibility (eq. 72): requires a result state that can be
re-achieved without a blocking threshold. PFC verbs always qualify.
COS verbs qualify when the outcome is not permanently destructive
(verb-specific; see LevinClass.reCompatible).
Equations
Instances For
Map @cite{levin-1993} classes to force transmission classes.
NOTE: reclassifies some traditionally COS classes as PFC.
The bend class (45.2) has changeOfState = true per @cite{levin-1993} but
receives multi-membered outcomes per: fold can yield
many different states (slightly creased, halfway bent, tightly folded, etc.).
This is a refinement, not a contradiction — Bhadra's VRO framework captures
finer-grained distinctions within COS.
Equations
- LevinClass.coil.forceTransmissionClass = ForceTransmissionClass.potentialForChange
- LevinClass.bend.forceTransmissionClass = ForceTransmissionClass.potentialForChange
- LevinClass.hit.forceTransmissionClass = ForceTransmissionClass.impingementEffecting
- LevinClass.swat.forceTransmissionClass = ForceTransmissionClass.impingementEffecting
- LevinClass.wipe.forceTransmissionClass = ForceTransmissionClass.impingementEffecting
- LevinClass.touch.forceTransmissionClass = ForceTransmissionClass.impingementEffecting
- LevinClass.break_.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.destroy.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.cooking.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.otherCoS.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.entitySpecificCoS.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.calibratableCoS.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.color.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.imageCreation.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.build.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.create.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.grow.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.knead.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.turn.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.cut.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.carve.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.eat.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.devour.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.murder.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.poison.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.mix.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.amalgamate.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.separate.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.split.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.conceal.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.clear.forceTransmissionClass = ForceTransmissionClass.integralChange
- LevinClass.dress.forceTransmissionClass = ForceTransmissionClass.integralChange
- x✝.forceTransmissionClass = ForceTransmissionClass.noForceTransmission
Instances For
re- compatibility at the Levin class level.
Within COS, re- is blocked when the outcome permanently eliminates or irreversibly transforms the object. Consumption verbs (*redestroy, *reeat) and killing verbs (*remurder) block re-. Physical property, creation, and degree achievement verbs allow re- (repaint, rebuild, refill).
Equations
- LevinClass.coil.reCompatible = true
- LevinClass.bend.reCompatible = true
- LevinClass.break_.reCompatible = true
- LevinClass.color.reCompatible = true
- LevinClass.imageCreation.reCompatible = true
- LevinClass.build.reCompatible = true
- LevinClass.create.reCompatible = true
- LevinClass.grow.reCompatible = true
- LevinClass.knead.reCompatible = true
- LevinClass.otherCoS.reCompatible = true
- LevinClass.cooking.reCompatible = true
- LevinClass.calibratableCoS.reCompatible = true
- LevinClass.clear.reCompatible = true
- LevinClass.entitySpecificCoS.reCompatible = true
- LevinClass.conceal.reCompatible = true
- LevinClass.dress.reCompatible = true
- LevinClass.separate.reCompatible = true
- LevinClass.mix.reCompatible = true
- LevinClass.amalgamate.reCompatible = true
- LevinClass.destroy.reCompatible = false
- LevinClass.eat.reCompatible = false
- LevinClass.devour.reCompatible = false
- LevinClass.murder.reCompatible = false
- LevinClass.poison.reCompatible = false
- LevinClass.turn.reCompatible = false
- LevinClass.cut.reCompatible = false
- LevinClass.carve.reCompatible = false
- LevinClass.split.reCompatible = false
- LevinClass.hit.reCompatible = false
- LevinClass.swat.reCompatible = false
- LevinClass.wipe.reCompatible = false
- LevinClass.touch.reCompatible = false
- x✝.reCompatible = false
Instances For
Only PFC has multi-membered outcomes.
PFC is the unique class compatible with both un- and re-.
IE is incompatible with both affixes.
COS is un-incompatible but re-compatible (class-level;
verb-specific blocking handled by LevinClass.reCompatible).
No-force verbs are incompatible with both.
PFC classification is orthogonal to the template-level
hasResultState property. Bend (45.2) has a result state (accomplishment
template) but coil (9.6) does not (putting template lacks BECOME). Both are
PFC — outcome cardinality captures a different dimension than template shape.
reclassifies bend (45.2) from COS to PFC despite Levin's CoS=true meaning components. This is the central refinement.
IE verbs map to the motionContact template (for wipe class) or activity template (for hit class).
PFC/IE distinction refines @cite{beavers-2010}'s
potential degree. Both PFC and IE objects have causallyAffected
without changeOfState, mapping to AffectednessDegree.potential.
But they differ in outcome cardinality:
PFC → multi (reversible), IE → singleton (irreversible impingement).
The kick object profile (canonical IE) maps to .nonquantized because
it has CoS=true; the prototypical PFC profile (CA+St, no CoS) maps
to .potential.
Result roots (@cite{beavers-etal-2021}) lexically entail change and thus have singleton outcome sets — the entailed result IS the single outcome. PC roots do not entail change, so their outcome cardinality depends on their force transmission class (COS vs PFC).
PC roots allow restitutive 'again' (@cite{beavers-etal-2021}), which aligns with prediction: verbs with multi-membered outcome sets (PFC verbs) can return to a prior state. Result roots cannot, because their singleton outcome is deterministically entailed.
A state function maps a time point to a lifespan point (property bundle) of an entity (eq. 53).
A lifespan point l(x) is a bundle of properties that an entity x has
at a point in its lifespan. The state function connects time to properties
via lifespan indexing.
Equations
- StateFunction Entity State Time = (Time → Entity → State)
Instances For
The APPLIES meta-predicate (eq. 59): the force associated with event e is being exerted on entity x.
This ensures the verb denotes a dynamic process that happened to x, filtering out stative verbs (which have no force transmission).
Equations
- Applies Entity Time = (Entity → Semantics.Events.Ev Time → Prop)
Instances For
Verb-Root-Outcomes: the compositional bundle for a dynamic transitive verb root (eq. 60).
Each verb root is lexically equipped with:
verb: the verb's denotation (entity × event predicate)outcomes: the set of possible result states after force transmissionthresholds: the set of contextually determined pre-states
For PFC verbs, outcomes is multi-membered (fold can yield slightly bent,
halfway bent, tightly folded, etc.). For COS verbs, outcomes is a
singleton. For IE verbs, outcomes is a singleton (surface alteration).
For no-force verbs, outcomes is empty.
- verb : Entity → Semantics.Events.Ev Time → Prop
The verb's truth-conditional predicate: verb(e)(x)
- applies : Entity → Semantics.Events.Ev Time → Prop
APPLIES: force transmission predicate
- outcomes : Set State
Set of outcomes: possible result states of the object (eq. 56a)
- thresholds : Set State
Set of thresholds: possible pre-states of the object (eq. 56b)
Instances For
Result state: the state of entity x at the right boundary of event e (eq. 64).
res(e)(x) := stateAt(RB(τ(e)))(x) — the property bundle of x
at the temporal right boundary of event e. This is NOT a temporal
operator; it yields a lifespan point (state).
Instances For
Pre-state: the state of entity x at the left boundary of event e (eq. 65).
pre(e)(x) := stateAt(LB(τ(e)))(x) — the property bundle of x
at the temporal left boundary of event e.
Instances For
Full semantics of reversative un- (eq. 66).
⟦un-⟧ᵍ := λP.λx.λe. [∃e': P(e')(x) ∧ APPLIES(e')(x) ∧ τ(e') ≪ τ(e) ∧ res(e')(x) = pre(e)(x) ∧ |O| > 1] ∧ res(e)(x) = pre(e')(x)
The APPLIES condition ensures force was exerted on x in the base event.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Presupposition of restitutive re- (eq. 68, first line).
There exists a prior event e' such that:
- The base verb P holds of e' and x
- APPLIES(e')(x) — force was exerted on x in the prior event
- The prior event temporally precedes the re-event: τ(e') ≪ τ(e)
- Result-state equivalence: res(e)(x) = res(e')(x)
Equations
Instances For
Full semantics of restitutive re- (eq. 68).
⟦re-⟧ᵍ := λP.λx.λe. [∃e': P(e')(x) ∧ APPLIES(e')(x) ∧ τ(e') ≪ τ(e) ∧ res(e)(x) = res(e')(x)] ∧ APPLIES(e)(x) ∧ P(e)(x)
The APPLIES conditions ensure force transmission in both the prior and re-events. This is what compositionally blocks re-destroy: after destruction, APPLIES fails for the re-event because force cannot be exerted on a non-existent object.
Equations
Instances For
Singleton outcome sets cannot satisfy the multi-membered presupposition
of un-. If a verb's outcome set has exactly one member, unSem is
unsatisfiable (because multiMembered requires two distinct elements).
This derives the distributional prediction: COS and IE verbs block un-
because their singleton outcome sets fail the |O| > 1 presupposition.
Empty outcome sets also block un-. If a verb exerts no force (no outcomes), the multi-membered presupposition trivially fails.