Root Quality Dimensions and Structural Entailments #
@cite{talmy-1988} @cite{talmy-2000} @cite{dowty-1991} @cite{beavers-koontz-garboden-2020} @cite{majid-boster-bowerman-2008}
Per-root content typology: ranges over root quality dimensions, the @cite{beavers-koontz-garboden-2020} (B&KG) binary entailment tetrad, and Marantz-style root structural position.
Provenance #
Moved from Core/Lexical/RootFeatures.lean in the cleanup that
dissolved Core/Lexical/. The file's original docstring claimed
"framework-agnostic infrastructure" but its load-bearing content
(B&KG's binary [state, manner, result, cause] tetrad in §3, Marantz's
complement-vs-adjunct merge position in §4) is framework-specific:
B&KG's tetrad is the thesis of @cite{beavers-koontz-garboden-2020},
explicitly opposed to Rappaport Hovav & Levin's template-based
account (@cite{rappaport-hovav-levin-2010}) and to Embick's
contextual-allosemy framework. Promoting these features to a named
Theories file (sibling of Roots/Basic.lean, Roots/Typology.lean,
Roots/Template.lean) makes the framework commitment legible.
Sibling slots intentionally unfilled. Theories/Semantics/Lexical/Roots/RappaportHovavLevin.lean
is the natural home for the template-based competitor account
(@cite{rappaport-hovav-levin-2010}, @cite{rappaport-hovav-levin-2024}).
@cite{rappaport-hovav-levin-2010} reject the very feature setup
encoded here; their position is that manner/result are
event-structural templates, not root features. The slot is empty
in this restructure; future work formalizing RH&L's framework
should land there as a sibling, with refutation theorems showing
where B&KG and RH&L disagree on attested verbs.
Sections #
- §1 Range mechanism —
Range α := Option (List α)for within-class variation - §2 Quality dimensions — force, robustness, instrument, dimensionality, agent properties
- §3 B&KG root structural entailments — state/manner/result/cause + collocational constraints
- §4 Marantz root structural position — complement vs adjunct of v
- §5 Derived properties on
RootProfile
Citation hygiene notes #
- B&KG page references (e.g., "Table 12, p. 228", "p. 229") are flagged
UNVERIFIED:per CLAUDE.md ("Never cite specific page ranges from memory"). Verify against the published @cite{beavers-koontz-garboden-2020} monograph before treating as authoritative. - Inline
Marantz (2009a;b, 2013)references in the original file lacked bib entries. The substantive claim — that roots merge as complement or adjunct of v — is uncontroversially attributed to Marantz across the DM literature, but the specific publication citations need verification before adding toreferences.bib.
Acceptable values along a quality dimension.
none: the root is unconstrained on this dimension (says nothing)some [v₁, v₂, …]: the root is compatible with exactly these values
Roots are regions, not points: a verb like tear is compatible with a range of force levels, not a single one.
Equations
- Semantics.Lexical.Roots.Range α = Option (List α)
Instances For
Equations
Instances For
Equations
- Semantics.Lexical.Roots.Range.only vs = some vs
Instances For
Equations
- Semantics.Lexical.Roots.Range.isCompatible none x✝ = true
- Semantics.Lexical.Roots.Range.isCompatible (some vs) x✝ = vs.contains x✝
Instances For
Equations
- Semantics.Lexical.Roots.Range.isConstrained none = false
- Semantics.Lexical.Roots.Range.isConstrained (some val) = true
Instances For
Two ranges overlap if they share at least one value.
Equations
- Semantics.Lexical.Roots.Range.overlaps none x✝ = true
- x✝.overlaps none = true
- Semantics.Lexical.Roots.Range.overlaps (some vs₁) (some vs₂) = vs₁.any fun (x : α) => vs₂.contains x
Instances For
Magnitude of force involved in the event.
@cite{talmy-1988} identifies force magnitude as a core parameter of force-dynamic schemas. @cite{spalek-mcnally-2026}: tear implies considerable force; rasgar implies less (enough to damage something flimsy).
- none : ForceLevel
- low : ForceLevel
- moderate : ForceLevel
- high : ForceLevel
Instances For
Equations
- Semantics.Lexical.Roots.instDecidableEqForceLevel x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
Equations
- One or more equations did not get rendered due to their size.
Instances For
Spatial pattern of force application.
@cite{talmy-2000}: force vectors have directional parameters. @cite{spalek-mcnally-2026}: tear implies contrary-direction force (pulling apart); rasgar implies unidirectional force (gash-like).
- none : ForceDirection
- unidirectional : ForceDirection
- bidirectional : ForceDirection
- omnidirectional : ForceDirection
Instances For
Equations
- Semantics.Lexical.Roots.instDecidableEqForceDirection x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Material substantiality of the affected entity (patient).
@cite{spalek-mcnally-2026}: the primary dimension distinguishing tear (unrestricted) from rasgar (flimsy patients only).
- insubstantial : Robustness
- flimsy : Robustness
- moderate : Robustness
- robust : Robustness
Instances For
Equations
- Semantics.Lexical.Roots.instDecidableEqRobustness x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Nature of the physical change produced by the event.
Grounded in @cite{levin-1993}'s class descriptions and @cite{hale-keyser-1987} notion of "separation in material integrity":
- 45.1 Break: loss of material integrity (break, crack, shatter, tear)
- 45.2 Bend: change in shape without loss of integrity
- 44 Destroy: total destruction (no specific resulting state)
- 21 Cut: separation via instrument contact Refined by @cite{beavers-koontz-garboden-2020} on CoS root types. UNVERIFIED: Levin chapter numbers cited from memory.
- separation : ResultType
- surfaceBreach : ResultType
- fracture : ResultType
- fragmentation : ResultType
- deformation : ResultType
- totalDestruction : ResultType
Instances For
Equations
- Semantics.Lexical.Roots.instDecidableEqResultType x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
Equations
- One or more equations did not get rendered due to their size.
Instances For
Type of instrument used in the event.
@cite{majid-boster-bowerman-2008}: instrument type interacts with object properties to determine the predictability of separation locus (their Dimension 1). Sharp instruments yield predictable separations; blunt instruments and hands yield unpredictable separations.
@cite{levin-1993}: cut verbs specify their instrument
(instrumentSpec = true); break verbs do not.
UNVERIFIED: Levin chapter (§21 vs §45.1) cited from memory.
- sharpBlade : InstrumentType
- bluntImpact : InstrumentType
- hands : InstrumentType
- none : InstrumentType
Instances For
Equations
- Semantics.Lexical.Roots.instDecidableEqInstrumentType x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dimensionality of the affected object (patient).
@cite{majid-boster-bowerman-2008}: object dimensionality interacts with instrument type and manner of action to determine event categorization cross-linguistically. 1D objects (rope, stick) can be snapped; 2D objects (cloth, paper) can be torn; 3D objects (melon, pot) can be smashed.
- oneD : ObjectDimensionality
- twoD : ObjectDimensionality
- threeD : ObjectDimensionality
Instances For
Equations
- Semantics.Lexical.Roots.instDecidableEqObjectDimensionality x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Whether the agent acts with volitional intent.
@cite{dowty-1991}: Proto-Agent entailment P1 = "volitional involvement in the event or state." @cite{ausensi-yu-smith-2021}: killing verb roots impose specific intentionality requirements on the agent (murder requires intentional agent; kill does not). @cite{levin-1993}: some break verbs "allow unintentional, action interpretations with body-part objects."
- nonvolitional : Volitionality
- neutral : Volitionality
- volitional : Volitionality
Instances For
Equations
- Semantics.Lexical.Roots.instDecidableEqVolitionality x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
Equations
- One or more equations did not get rendered due to their size.
Instances For
Whether the action can be performed with care and control.
@cite{dowty-1991}: Proto-Agent entailment P2 = "sentience (and/or perception)," enabling controlled action. @cite{spalek-mcnally-2026}: tear is compatible with careful action ("carefully tore the tin foil"); rasgar is not ("??rasgaron con cuidado el papel").
- incompatible : AgentControl
- neutral : AgentControl
- compatible : AgentControl
Instances For
Equations
- Semantics.Lexical.Roots.instDecidableEqAgentControl x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Within-class root content profile.
Captures quality dimensions of root content — force, robustness,
agent properties — as opposed to RootEntailments (§ 3), which
captures structural entailments (state, manner, result, cause).
Each dimension is a Range of acceptable values; none means the
root says nothing about that dimension (unconstrained).
Together with MeaningComponents (which defines the class),
LevinClass (which identifies the class), and RootEntailments
(which captures structural entailments), this gives a four-level
characterization of a verb's semantic content:
- Class-defining meaning components (binary, from alternations)
- Class membership (Levin taxonomy)
- Root structural entailments (@cite{beavers-koontz-garboden-2020})
- Root-specific quality features (ranges, from detailed lexical analysis)
- forceMag : Range ForceLevel
Force magnitude: @cite{talmy-1988}.
- forceDir : Range ForceDirection
Force directionality: @cite{talmy-2000}, @cite{spalek-mcnally-2026}.
- patientRob : Range Robustness
Patient material robustness: @cite{spalek-mcnally-2026}.
- resultType : Range ResultType
Type of physical change: @cite{levin-1993}, @cite{beavers-koontz-garboden-2020}.
- agentVolition : Range Volitionality
Agent volitionality: @cite{dowty-1991} P1, @cite{ausensi-yu-smith-2021}.
- agentControl : Range AgentControl
Agent control: @cite{dowty-1991} P2, @cite{spalek-mcnally-2026}.
- instrumentType : Range InstrumentType
Instrument type the root selects for: @cite{majid-boster-bowerman-2008}. cut selects for sharp blades; break is unspecified.
- patientDim : Range ObjectDimensionality
Patient dimensionality: @cite{majid-boster-bowerman-2008}. tear selects for 2D objects (cloth, paper); snap for 1D (stick, twig).
Instances For
Equations
- One or more equations did not get rendered due to their size.
- Semantics.Lexical.Roots.instBEqRootProfile.beq x✝¹ x✝ = false
Instances For
Equations
Equations
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Root-level structural entailments from @cite{beavers-koontz-garboden-2020}.
B&KG argue against Bifurcation (roots only contribute idiosyncratic content) and Manner/Result Complementarity (no root encodes both). Roots CAN entail states, change, and causation — notions traditionally reserved for templates (CAUSE, BECOME).
The four features define a root typology:
state: root describes a state (√FLAT, √CRACK, √DRY)manner: root describes an action/manner (√JOG, √RUN, √HIT)result: root entails change — passes restitutive again testcause: root entails causation
Constraints: result → state and cause → result (see WellFormed).
@cite{rappaport-hovav-levin-2010} reject this entailment-feature
framing; for them manner/result are event-structural template
properties, not root features. The competitor analysis would live
in Theories/Semantics/Lexical/Roots/RappaportHovavLevin.lean (planned).
UNVERIFIED: B&KG Table 12 reference cited from memory.
- state : Bool
- manner : Bool
- result : Bool
- cause : Bool
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
If a root entails change (result), it entails a state that changes. @cite{beavers-koontz-garboden-2020}: result entailments presuppose state entailments.
Equations
- r.ResultImpliesState = (r.result = true → r.state = true)
Instances For
Equations
- r.instDecidableResultImpliesState = id inferInstance
If a root entails causation, it entails what is caused (a result). @cite{beavers-koontz-garboden-2020}: cause entailments presuppose result entailments.
Equations
- r.CauseImpliesResult = (r.cause = true → r.result = true)
Instances For
Equations
- r.instDecidableCauseImpliesResult = id inferInstance
Well-formedness: both collocational constraints hold.
Equations
- r.WellFormed = (r.ResultImpliesState ∧ r.CauseImpliesResult)
Instances For
Equations
- r.instDecidableWellFormed = id inferInstance
Canonical root types #
UNVERIFIED: Specific row references to @cite{beavers-koontz-garboden-2020} Table 12 are cited from memory. The 7 canonical types below cover B&KG's typology; verify row numbers against the published monograph before treating as definitive.
+S −M −R −C: property concept roots (√FLAT, √DRY). Deadjectival COS verbs — the root names the result state. Complement position.
Equations
- Semantics.Lexical.Roots.RootEntailments.propertyConcept = { state := true, manner := false, result := false, cause := false }
Instances For
+S −M +R −C: internally caused result roots (√BLOSSOM, √RUST). Root entails both a state and a change to that state, but not external causation. Complement position.
Equations
- Semantics.Lexical.Roots.RootEntailments.pureResult = { state := true, manner := false, result := true, cause := false }
Instances For
+S −M +R +C: externally caused result roots (√CRACK, √BREAK). Root entails a state, change, AND causation — the root inherently implies an external cause. Complement position. @cite{beavers-koontz-garboden-2020}: these "lexicalize crosslinguistically as basic causatives" unlike √BLOSSOM-type roots.
Equations
- Semantics.Lexical.Roots.RootEntailments.causativeResult = { state := true, manner := false, result := true, cause := true }
Instances For
−S +M −R −C: pure manner roots (√JOG, √RUN, √SWIM). Root specifies action manner without entailing any state. Adjoined position.
Equations
- Semantics.Lexical.Roots.RootEntailments.pureManner = { state := false, manner := true, result := false, cause := false }
Instances For
+S +M +R −C: manner + result without cause. Well-formed per the constraints but UNATTESTED in B&KG's typology. Such roots "would essentially derive syntactically unergative verbs with pure change-of-state meanings." Defined for completeness.
Equations
- Semantics.Lexical.Roots.RootEntailments.mannerResult = { state := true, manner := true, result := true, cause := false }
Instances For
+S +M +R +C: fully specified roots (√HAND, √DROWN, √CUT). @cite{beavers-koontz-garboden-2020} Ch. 3–4: manner + caused change. These are the attested MRC violators. √HAND sits in adjoined position, √DROWN in complement position; this structural difference is not captured here.
Equations
- Semantics.Lexical.Roots.RootEntailments.fullSpec = { state := true, manner := true, result := true, cause := true }
Instances For
−S −M −R −C: minimal roots — no structural entailments. Conservative default for classes not yet studied under B&KG's framework. Not a row in B&KG's typology (which only lists roots with at least one positive feature).
Equations
- Semantics.Lexical.Roots.RootEntailments.minimal = { state := false, manner := false, result := false, cause := false }
Instances For
Canonical type well-formedness #
MRC violation detection #
Does this root violate Manner/Result Complementarity? @cite{beavers-koontz-garboden-2020} Ch. 4: some roots encode both manner and result. @cite{rappaport-hovav-levin-2010} dispute this; the framing "violates MRC" presupposes MRC as a baseline norm — itself a framework commitment.
Equations
- r.ViolatesMRC = (r.manner = true ∧ r.result = true)
Instances For
Equations
- r.instDecidableViolatesMRC = id inferInstance
Structural attachment position of a verb root. Following the Distributed-Morphology tradition (Marantz; systematized by @cite{beavers-koontz-garboden-2020}):
- Complement: root merges as complement of v (inside VP). Fills the result-state slot. Change-of-state roots: √FLAT, √CRACK, √BLOSSOM, √DROWN.
- Adjoined: root merges as adjunct to v (outside VP). Modifies the causing event. Manner/activity roots: √JOG, √TOSS, √HAND.
This distinction is structurally significant beyond root typology: it determines vVPE eligibility (@cite{kalyakin-2026}), scope of result-state modifiers, and the restitutive/repetitive again ambiguity (@cite{beavers-koontz-garboden-2020}, @cite{merchant-2013}).
UNVERIFIED: The Marantz publications usually cited in this
context (DM "Phases and words" handout, "No Escape from Syntax",
"Verbal argument structure" chapter) have not been added to
references.bib. The substantive claim is uncontroversially
attributed to Marantz across DM, but specific publication
references should be verified before citing.
Note: this is the canonical RootPosition for the Roots/
subdirectory; Template.lean will be updated in the same restructure
commit to drop its local duplicate def and import from here.
- complement : RootPosition
- adjoined : RootPosition
Instances For
Equations
- Semantics.Lexical.Roots.instDecidableEqRootPosition x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Does a root profile constrain patient properties?
Equations
- rp.constrainsPatient = (rp.patientRob.isConstrained = true)
Instances For
Do two root profiles overlap (share at least one compatible event)?
Equations
- One or more equations did not get rendered due to their size.