Steedman 2000: The Syntactic Process #
CCG predictions from [Ste00a], one section per phenomenon:
- Word order: slash direction in lexical categories enforces English SVO.
- Non-constituent coordination: type-raising + composition make "John
likes" a constituent (
S/NP), and generalized conjunction delivers the conjunctive interpretation (modeled on the book's "Anna married, and I detest, Manny"). - Gapping: [Ros70]'s word-order/gapping-direction generalization, recovered from the type-raising directions a language's verb categories license.
- Cross-serial dependencies: Dutch verb clusters ([BKPZ82]) with cross-serial NP-verb bindings, via the book's leftward argument categories and forward crossed composition.
- Verb clusters and quantifier scope (§6.8): verb-raising orders are
scope-ambiguous, verb-projection-raising orders surface-only; predictions
are computed via
CCG.Scope.analyzeDerivationand checked against the §6.8 judgments inLinglib.Data.Examples.Steedman2000([Bay96], [Kay98], [HvR86], [Hae92] are credited per example in the JSON).
Word order #
Slash direction encodes word order: TV = (S\NP)/NP looks right for the
object NP first, then the resulting S\NP looks left for the subject,
enforcing SVO.
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
- One or more equations did not get rendered due to their size.
Instances For
Non-constituent coordination #
CCG derives "John likes and Mary hates beans" (modeled on the book's
"Anna married, and I detest, Manny") with category S: "John likes" is a
constituent S/NP via type-raising + composition.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Non-constituent coordination requires more combinatory operations than standard coordination. Reading operation count as processing difficulty is this formalization's linking hypothesis, not a claim of [Ste00a].
Toy semantic lexicon over the toy English fragment ("likes"/"hates"
reuse sees_sem as placeholder denotations).
Equations
- One or more equations did not get rendered due to their size.
- Steedman2000.toySemLexicon "John" (CCG.Cat.atom CCG.Atom.NP) = some { cat := CCG.NP, meaning := Semantics.Montague.ToyEntity.john }
- Steedman2000.toySemLexicon "Mary" (CCG.Cat.atom CCG.Atom.NP) = some { cat := CCG.NP, meaning := Semantics.Montague.ToyEntity.mary }
- Steedman2000.toySemLexicon "beans" (CCG.Cat.atom CCG.Atom.NP) = some { cat := CCG.NP, meaning := Semantics.Montague.ToyEntity.pizza }
- Steedman2000.toySemLexicon "sleeps" ((CCG.Cat.atom CCG.Atom.S).lslash (CCG.Cat.atom CCG.Atom.NP)) = some { cat := CCG.IV, meaning := Semantics.Montague.ToyLexicon.sleeps_sem }
- Steedman2000.toySemLexicon "laughs" ((CCG.Cat.atom CCG.Atom.S).lslash (CCG.Cat.atom CCG.Atom.NP)) = some { cat := CCG.IV, meaning := Semantics.Montague.ToyLexicon.laughs_sem }
- Steedman2000.toySemLexicon word cat = none
Instances For
"John sees Mary" with a type-raised subject: the raised subject
CCG.john_tr : S/(S\NP) uses forward application, and the derivation
produces the same truth value as the canonical one.
Equations
- Steedman2000.john_sees_mary_via_tr = CCG.john_tr.fapp ((CCG.DerivStep.lex { form := "sees", cat := CCG.TV }).fapp (CCG.DerivStep.lex { form := "Mary", cat := CCG.NP }))
Instances For
The predicate "John likes and Mary hates" (category S/NP) evaluated
at an entity.
Equations
- Steedman2000.coordMeaningAt e = Option.map (fun (x : Semantics.Montague.ToyEntity → Prop) => x e) (CCG.getPredicateMeaning (CCG.john_likes_and_mary_hates.interp Steedman2000.toySemLexicon))
Instances For
The pointwise conjunction of "John likes" and "Mary hates" at an entity.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Generalized conjunction delivers the conjunctive interpretation: ⟦John likes and Mary hates⟧(e) = ⟦John likes⟧(e) ∧ ⟦Mary hates⟧(e).
The truth conditions of "John likes and Mary hates beans" are the conjunction of the two predications (in the toy model, likes = hates = sees).
The spelled-out paraphrase "John likes beans and Mary hates beans".
Equations
- One or more equations did not get rendered due to their size.
Instances For
The non-constituent coordination and its spelled-out paraphrase receive the same truth conditions — the book's claim that the composed derivation yields the same predicate-argument structure as the canonical one.
The coordinator's role is truth-conditionally load-bearing #
interp reads the coordinator's role off the .coord node — it no longer hardcodes
conjunction — so which coordinator a derivation uses is part of its truth conditions.
Using the actual English fragment coordinators, conjoining a true sentence p and a false
sentence q with and_ (role = .j) gives p ∧ q (false), while or_ (role = .disj)
gives p ∨ q (true). They differ, so the marking's role field is load-bearing — flipping
English.Coordination.and_.role to .disj would break the theorem below, rather than no
theorem depending on it.
The coordinator's role flips the truth conditions: English and_ yields p ∧ q,
or_ yields p ∨ q, and these differ at p = ⊤, q = ⊥. Flipping a fragment
coordinator's role collapses the inequality, so the role marking is not decorative.
Gapping #
[Ros70]'s generalization — gapping direction tracks word order —
which [Ste00a] derives from the Principles of Adjacency,
Consistency, and Inheritance together with the order-preserving constraint
on type-raising. Deriving predictedGappingPattern from the slash
directions of CCG.Gapping's gapped categories is TODO.
(Dutch licensing both directions is mixed_allows_both.)
Equations
- Steedman2000.instDecidableEqWordOrder 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
- Steedman2000.instReprWordOrder = { reprPrec := Steedman2000.instReprWordOrder.repr }
Direction of gapping in a coordinate structure: forward gapping leaves the gap in the non-initial conjunct ("Dexter ate bread, and Warren, potatoes"); backward gapping leaves it in the non-final conjunct (Japanese "Ken-ga Naomi-o, Erika-ga Sara-o tazuneta").
- forward : GappingDirection
- backward : GappingDirection
Instances For
Equations
- Steedman2000.instDecidableEqGappingDirection 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
The gapping directions a language allows.
- allowsForward : Prop
- allowsBackward : Prop
- decAllowsForward : Decidable self.allowsForward
- decAllowsBackward : Decidable self.allowsBackward
Instances For
Equations
- Steedman2000.GappingPattern.forwardOnly = { allowsForward := True, allowsBackward := False, decAllowsForward := instDecidableTrue, decAllowsBackward := instDecidableFalse }
Instances For
Equations
- Steedman2000.GappingPattern.backwardOnly = { allowsForward := False, allowsBackward := True, decAllowsForward := instDecidableFalse, decAllowsBackward := instDecidableTrue }
Instances For
Equations
- Steedman2000.GappingPattern.both = { allowsForward := True, allowsBackward := True, decAllowsForward := instDecidableTrue, decAllowsBackward := instDecidableTrue }
Instances For
Equations
- Steedman2000.GappingPattern.neither = { allowsForward := False, allowsBackward := False, decAllowsForward := instDecidableFalse, decAllowsBackward := instDecidableFalse }
Instances For
[Ros70]'s generalization: verb-final orders gap backward, the rest gap forward.
Equations
- Steedman2000.rossOriginal Steedman2000.WordOrder.SOV = Steedman2000.GappingPattern.backwardOnly
- Steedman2000.rossOriginal Steedman2000.WordOrder.VSO = Steedman2000.GappingPattern.forwardOnly
- Steedman2000.rossOriginal Steedman2000.WordOrder.SVO = Steedman2000.GappingPattern.forwardOnly
- Steedman2000.rossOriginal Steedman2000.WordOrder.VOS = Steedman2000.GappingPattern.forwardOnly
- Steedman2000.rossOriginal Steedman2000.WordOrder.OVS = Steedman2000.GappingPattern.backwardOnly
- Steedman2000.rossOriginal Steedman2000.WordOrder.OSV = Steedman2000.GappingPattern.backwardOnly
Instances For
The order's transitive verbs seek (at least one of) their arguments rightward.
Equations
Instances For
Equations
- One or more equations did not get rendered due to their size.
The order's transitive verbs seek their arguments leftward.
Equations
Instances For
Equations
- One or more equations did not get rendered due to their size.
The gapping directions CCG predicts for a word order: forward gapping
needs a leftward-looking gapped conjunct, available through backward
type-raising over rightward-seeking verbs (T\(T/NP)); backward gapping
needs forward raising over leftward-seeking verbs (T/(T\NP)).
Equations
- One or more equations did not get rendered due to their size.
Instances For
The CCG-predicted pattern coincides with Ross's generalization.
SVO patterns with VSO: both license forward but not backward gapping.
English (SVO) has no leftward-looking transitive verb category, so the
rightward-looking gapped conjunct a backward gap needs cannot be built:
"*Warren, potatoes and Dexter ate bread" (instantiating Steedman's
*SO and SVO schema; the book's attested forward counterpart is "Dexter
ate bread and Warren, potatoes").
Main- vs subordinate-clause word order, for languages whose two clause types diverge.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Steedman's revision of [Ros70]: gapping availability tracks the lexical availability of verb categories, not a single "underlying" word order — forward gapping needs rightward-combining verbs, backward gapping leftward-combining verbs in either clause type.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dutch: SVO main clauses, SOV subordinate clauses. The mixed profile licenses both gapping directions — forward in main clauses ("Wil jij een ijsje en Marietje limonade?"), backward in subordinate clauses ("...dat Jan Syntactic Structures en Piet Aspects gelezen heeft").
Equations
- Steedman2000.dutch = { mainClause := Steedman2000.WordOrder.SVO, subClause := Steedman2000.WordOrder.SOV }
Instances For
A mixed-order language like Dutch licenses both gapping directions.
Steedman's taxonomy of elliptical constructions.
- gapping : EllipsisType
"Dexter ate bread, and Warren, potatoes"
- stripping : EllipsisType
"Dexter ran away, and Warren (too)"
- vpEllipsis : EllipsisType
"Dexter ate bread, and Warren did too"
- sluicing : EllipsisType
"Dexter did something, but I don't know what"
Instances For
Equations
- Steedman2000.instDecidableEqEllipsisType x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
- Steedman2000.instReprEllipsisType = { reprPrec := Steedman2000.instReprEllipsisType.repr }
Equations
- One or more equations did not get rendered due to their size.
Instances For
Gapping and stripping are syntactically mediated via CCG; VP ellipsis and sluicing are purely anaphoric.
Equations
- Steedman2000.isSyntacticallyMediated Steedman2000.EllipsisType.gapping = True
- Steedman2000.isSyntacticallyMediated Steedman2000.EllipsisType.stripping = True
- Steedman2000.isSyntacticallyMediated Steedman2000.EllipsisType.vpEllipsis = False
- Steedman2000.isSyntacticallyMediated Steedman2000.EllipsisType.sluicing = False
Instances For
Equations
- One or more equations did not get rendered due to their size.
Only the syntactically mediated ellipsis types exhibit word-order constraints; VP ellipsis and sluicing pattern alike across languages.
Equations
- Steedman2000.HasWordOrderConstraints Steedman2000.EllipsisType.gapping = True
- Steedman2000.HasWordOrderConstraints Steedman2000.EllipsisType.stripping = True
- Steedman2000.HasWordOrderConstraints Steedman2000.EllipsisType.vpEllipsis = False
- Steedman2000.HasWordOrderConstraints Steedman2000.EllipsisType.sluicing = False
Instances For
Equations
- One or more equations did not get rendered due to their size.
All four of Steedman's elliptical constructions are surface anaphora in
Hankamer & Sag's sense ([HS76]): each deletes internal structure
under identity with a linguistic antecedent. Steedman's taxonomy contains no
deep anaphor (no do so-type pro-form), so the depth axis is constant
.surface over it.
Equations
- Steedman2000.instHasDepthEllipsisType = { depth := fun (x : Steedman2000.EllipsisType) => Anaphor.Depth.surface }
Cross-framework non-alignment. Steedman's CCG cut isSyntacticallyMediated
(gapping/stripping derived by category composition; VP-ellipsis/sluicing handled
anaphorically) is not Hankamer & Sag's deep/surface cut. VP-ellipsis is the
paradigm surface anaphor ([HS76]; Landau's own surface baseline in
[Lan26]) yet CCG treats it as non-mediated — so the two frameworks partition
the very same constructions differently.
Cross-serial dependencies #
Dutch verb clusters ([BKPZ82]) with cross-serial NP-verb
bindings, using the surface-faithful derivations of CCG.CrossSerial:
cluster verbs carry leftward NP slots and the cluster composes by forward
crossed composition, per the book's own Dutch fragment, so the yield
matches the attested word order.
A CCG derivation annotated with which NP binds to which verb.
TODO: compute binding from deriv's composition structure instead of
annotating it by hand.
- n : ℕ
Number of NP-verb pairs
- deriv : CCG.Classical.Derivation
- words : List String
Surface words
- binding : Features.VerbClusterBinding self.n
The NP-verb binding permutation
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
"Jan Piet zag zwemmen" with cross-serial bindings: Jan is the subject of "zag", Piet the argument bound into the cluster.
Equations
- One or more equations did not get rendered due to their size.
Instances For
"Jan Piet Marie zag helpen zwemmen": zag >B× (helpen zwemmen) makes
the cluster a leftward-seeking 3-place predicate; Marie binds helpen's
slot, Piet zag's object slot, Jan the subject — the cross-serial
binding pattern, in the attested word order.
Equations
- One or more equations did not get rendered due to their size.
Instances For
The annotated binding agrees with the empirical datum.
The derivations spell out exactly the annotated surface words.
Verb clusters and quantifier scope (§6.8) #
Scope tracks word order: in the verb-raising order the cluster forms by
composition, so a quantified argument combines with a function containing
the tensed verb and can take scope over it; in the verb-projection-raising
order it combines with the embedded verb alone. The derivations below are
category-checked DerivStep trees: the verb-raising cluster forms by
forward crossed composition (CCG.forwardCompX), the
verb-projection-raising order by plain application — the composed-cluster
vs. applied-cluster contrast driving the account. (The toy Cat still
drops the book's features, e.g. the VP₋SUB restriction on >B×.)
Equations
- Steedman2000.instDecidableEqVerbOrder 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
- Steedman2000.instReprVerbOrder = { reprPrec := Steedman2000.instReprVerbOrder.repr }
Equations
Verb-raising order, Dutch (99a): the cluster probeert te zingen forms by crossed composition before taking the object to its left.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Verb-projection-raising order, Dutch (99b): the matrix verb applies to an already-saturated embedded VP, so the quantified object never combines with a function containing the tensed verb.
Equations
- One or more equations did not get rendered due to their size.
Instances For
The CCG derivation shape each verb order forces.
Equations
Instances For
Both derivations are category-valid and derive the same category.
Scope availability as CCG predicts it: analyze the derivation the word order forces and read availability off its derivation type.
Equations
Instances For
Read the §6.8 word-order classification off an example's
paperFeatures.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Observed scope availability: the judgment on the example's "inverse" reading (the "surface" reading is acceptable throughout §6.8).
Equations
- One or more equations did not get rendered due to their size.
Instances For
The §6.8 data as (word order, observed availability) pairs.
Equations
- One or more equations did not get rendered due to their size.
Instances For
The CCG prediction matches every §6.8 judgment.
Truth-conditional pipeline #
The complete CCG → Montague pipeline over the toy fragment: derivations interpreted compositionally, each checked against the toy model.
"John sleeps" - backward application
Equations
- Steedman2000.ccg_john_sleeps = (CCG.DerivStep.lex { form := "John", cat := CCG.NP }).bapp (CCG.DerivStep.lex { form := "sleeps", cat := CCG.IV })
Instances For
"Mary sleeps" - backward application
Equations
- Steedman2000.ccg_mary_sleeps = (CCG.DerivStep.lex { form := "Mary", cat := CCG.NP }).bapp (CCG.DerivStep.lex { form := "sleeps", cat := CCG.IV })
Instances For
"John laughs" - backward application
Equations
- Steedman2000.ccg_john_laughs = (CCG.DerivStep.lex { form := "John", cat := CCG.NP }).bapp (CCG.DerivStep.lex { form := "laughs", cat := CCG.IV })
Instances For
"Mary laughs" - backward application
Equations
- Steedman2000.ccg_mary_laughs = (CCG.DerivStep.lex { form := "Mary", cat := CCG.NP }).bapp (CCG.DerivStep.lex { form := "laughs", cat := CCG.IV })
Instances For
"John sees Mary" - forward then backward application
Equations
- One or more equations did not get rendered due to their size.
Instances For
"Mary sees John" - forward then backward application
Equations
- One or more equations did not get rendered due to their size.
Instances For
"John eats pizza" - forward then backward application
Equations
- One or more equations did not get rendered due to their size.
Instances For
Extended lexicon with all entities and predicates
Equations
- One or more equations did not get rendered due to their size.
- Steedman2000.extendedLexicon "John" (CCG.Cat.atom CCG.Atom.NP) = some { cat := CCG.NP, meaning := Semantics.Montague.ToyEntity.john }
- Steedman2000.extendedLexicon "Mary" (CCG.Cat.atom CCG.Atom.NP) = some { cat := CCG.NP, meaning := Semantics.Montague.ToyEntity.mary }
- Steedman2000.extendedLexicon "pizza" (CCG.Cat.atom CCG.Atom.NP) = some { cat := CCG.NP, meaning := Semantics.Montague.ToyEntity.pizza }
- Steedman2000.extendedLexicon "book" (CCG.Cat.atom CCG.Atom.NP) = some { cat := CCG.NP, meaning := Semantics.Montague.ToyEntity.book }
- Steedman2000.extendedLexicon "sleeps" ((CCG.Cat.atom CCG.Atom.S).lslash (CCG.Cat.atom CCG.Atom.NP)) = some { cat := CCG.IV, meaning := Semantics.Montague.ToyLexicon.sleeps_sem }
- Steedman2000.extendedLexicon "laughs" ((CCG.Cat.atom CCG.Atom.S).lslash (CCG.Cat.atom CCG.Atom.NP)) = some { cat := CCG.IV, meaning := Semantics.Montague.ToyLexicon.laughs_sem }
- Steedman2000.extendedLexicon word cat = none
Instances For
Get meaning (as Prop) from CCG derivation
Equations
Instances For
CCG correctly predicts "John sleeps" is true
CCG correctly predicts "Mary sleeps" is false
CCG correctly predicts "John laughs" is true
CCG correctly predicts "Mary laughs" is true
CCG correctly predicts "John sees Mary" is true
CCG correctly predicts "Mary sees John" is true