Causative Builder #
@cite{nadathur-lauer-2020} @cite{talmy-1988} @cite{wolff-2003}
Links causative verb lexical entries to their compositional semantics,
following the same pattern as PreferentialBuilder for attitude verbs.
Design principle #
The builder names a force-dynamic mechanism, not a causal-model property. Properties like "asserts sufficiency" or "asserts necessity" are derived from the builder via theorems.
| Builder | Mechanism | English verbs | N&L property (derived) |
|---|---|---|---|
| cause | Counterfactual dependence | cause | necessity |
| make | Direct sufficient guarantee | make, have, get | sufficiency |
| force | Coercive (overcome resistance) | force | sufficiency + coercion |
| enable | Barrier removal (permissive) | let, enable | sufficiency |
| prevent | Barrier addition (blocking) | prevent | preventSem |
How a causative verb's semantics is built from causal model infrastructure.
The builder names a force-dynamic mechanism, not a
causal-model property. toSemantics maps each builder to its
truth-condition function; properties like sufficiency/necessity are
derived via theorems.
cause: Counterfactual dependence — removing cause blocks effect.make: Direct sufficient guarantee — adding cause ensures effect.force: Coercive sufficiency — overcome resistance, no alternatives.enable: Permissive — remove barrier so effect can occur.prevent: Blocking — add barrier so effect cannot occur.
- cause : CausativeBuilder
Counterfactual dependence: removing cause → no effect. Semantic function:
causeSem. - make : CausativeBuilder
Direct sufficient guarantee: adding cause → effect. Semantic function:
makeSem. - force : CausativeBuilder
Coercive sufficiency: overcome resistance, no alternatives. Same truth conditions as
make; distinguished byisCoercive. - enable : CausativeBuilder
Permissive: remove barrier so effect can occur. Same truth conditions as
make; distinguished byisPermissive. - prevent : CausativeBuilder
Blocking: add barrier so effect cannot occur. Semantic function:
preventSem(dual ofcauseSem).
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- NadathurLauer2020.Builder.instBEqCausativeBuilder.beq x✝ y✝ = (x✝.ctorIdx == y✝.ctorIdx)
Instances For
Prevent semantics #
preventSem is the dual of causeSem: the preventer blocks an effect
that would otherwise occur.
Semantics of "prevent" (causative verb asserting blocking).
"X prevented Y" is true iff:
- With the preventer present, the effect does NOT occur
- Without the preventer, the effect WOULD have occurred
This is the dual of causeSem: cause asserts the effect depends on
the cause being present; prevent asserts the effect depends on the
preventer being absent.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Map a causative builder to its semantic function.
This is the structural link between the lexical annotation and the formal semantics. The builder NAMES the force-dynamic mechanism; this function provides the actual truth-condition computation.
Note: force and enable share makeSem truth conditions with make.
They differ in force-dynamic properties (coercion, permissivity),
which are captured by isCoercive and isPermissive.
Equations
- NadathurLauer2020.Builder.CausativeBuilder.cause.toSemantics = NadathurLauer2020.Necessity.causeSem
- NadathurLauer2020.Builder.CausativeBuilder.make.toSemantics = NadathurLauer2020.Sufficiency.makeSem
- NadathurLauer2020.Builder.CausativeBuilder.force.toSemantics = NadathurLauer2020.Sufficiency.makeSem
- NadathurLauer2020.Builder.CausativeBuilder.enable.toSemantics = NadathurLauer2020.Sufficiency.makeSem
- NadathurLauer2020.Builder.CausativeBuilder.prevent.toSemantics = NadathurLauer2020.Builder.preventSem
Instances For
Derived property functions #
These functions derive causal-model properties from the force-dynamic builder. They are the interface between the fine-grained builder and Nadathur & Lauer's binary sufficiency/necessity classification.
Does this builder assert causal sufficiency (N&L Def 23)?
DERIVED: true for builders whose toSemantics maps to makeSem.
Equations
- NadathurLauer2020.Builder.CausativeBuilder.make.assertsSufficiency = true
- NadathurLauer2020.Builder.CausativeBuilder.force.assertsSufficiency = true
- NadathurLauer2020.Builder.CausativeBuilder.enable.assertsSufficiency = true
- NadathurLauer2020.Builder.CausativeBuilder.cause.assertsSufficiency = false
- NadathurLauer2020.Builder.CausativeBuilder.prevent.assertsSufficiency = false
Instances For
Does this builder assert causal necessity (N&L Def 24)?
DERIVED: true only for .cause, whose toSemantics maps to causeSem.
Equations
Instances For
Does this builder encode coercion (overcoming resistance)?
Force-dynamic property: .force encodes that the causer overcame
the causee's resistance.
Instances For
Does this builder encode permissivity (barrier removal)?
Force-dynamic property: .enable encodes that the causer removed
a barrier, allowing the effect to occur naturally.
Equations
Instances For
Derivation theorems #
These theorems show that N&L's sufficiency/necessity classification is derivable from the force-dynamic builder, rather than being independently stipulated.
All sufficiency-asserting builders (make, force, enable) compute
truth conditions via makeSem.
The cause builder computes truth conditions via causeSem.
make and force have the same truth conditions.
Both map to makeSem. They are distinguished by isCoercive:
force lexically encodes coercion while make does not.
enable and make have the same truth conditions.
Both map to makeSem. They are distinguished by isPermissive:
enable encodes barrier removal while make does not.
cause asserts the effect depends on the cause being present;
prevent asserts the effect depends on the preventer being absent.
Formally: preventSem holds when effect is blocked WITH the preventer
and would occur WITHOUT it — the mirror of causeSem which holds when
effect occurs WITH the cause and wouldn't occur WITHOUT it.
At least two builders produce genuinely different truth conditions.
Witnessed by the overdetermination scenario (lightning + arsonist):
makeSem returns true (lightning sufficient) but causeSem returns
false (lightning not necessary).
make and force are distinguished by coercion despite sharing truth conditions.
make and enable are distinguished by permissivity despite sharing truth conditions.
Sufficiency-asserting builders all use makeSem.
This is the key bridge: assertsSufficiency exactly characterizes
builders whose toSemantics returns makeSem.
TODO: The prevent case requires showing preventSem ≠ makeSem,
which needs a witness (a model where they differ).
When a sufficiency builder's semantics holds, the cause is causally sufficient for the effect.
This is DERIVED: it follows from the fact that makeSem is defined
as causallySufficient.
When the cause builder's semantics holds, the cause is causally necessary for the effect.
DERIVED from the fact that causeSem conjoins occurrence
with causallyNecessary.