Keenan & Comrie (1977) @cite{keenan-comrie-1977} #
Noun Phrase Accessibility and Universal Grammar. Linguistic Inquiry 8(1): 63–99.
Formalizes the three Hierarchy Constraints (HCs) and the derived Primary Relativization Constraint (PRC) from @cite{keenan-comrie-1977}, verified against a subset of the paper's Table 1 data.
Hierarchy Constraints #
The paper proposes three constraints on how languages form relative clauses, building on the Accessibility Hierarchy (AH):
SU > DO > IO > OBL > GEN > OCOMP
- HC₁: A language must be able to relativize subjects.
- HC₂ (Continuity): Any RC-forming strategy must apply to a continuous segment of the AH.
- HC₃ (Cut-off): Strategies that apply at one point may cease at any lower point.
From HC₁ + HC₂, the Primary Relativization Constraint follows: if a language's primary strategy (one that covers subjects) can apply to a low position N, it can apply to all positions above N. Non-primary strategies need not satisfy this — they may cover a continuous segment that excludes subjects (e.g., the +case strategy covering IO–OCOMP but not SU–DO in Welsh and Arabic).
Multi-Strategy Profiles #
The paper's key empirical contribution is showing that languages typically have multiple relativization strategies, each covering a different contiguous segment of the AH. The ±case distinction (whether the relative element bears case marking) is the primary parameter distinguishing strategies.
Data #
Table 1 profiles are derived from fragment data — each language's
RelClauseMarker list (encoding actual linguistic markers: particles,
pronouns, verbal suffixes) is converted to StrategyEntry records.
This ensures the study file stays consistent with the fragment layer
by construction. We cover the key patterns: gap-to-resumptive split
(Welsh, Hebrew, Arabic, Toba Batak), multi-strategy with prenominal
RCs (Korean, Finnish), and single-strategy (Malagasy).
A single relativization strategy from @cite{keenan-comrie-1977} Table 1.
Each language has one or more strategies. A strategy is characterized by the position of the RC (pre/post-nominal), whether the relative element bears case marking (±case), and which AH positions it covers.
- rcPosition : Core.RCPosition
Position of relative clause with respect to head noun
- plusCase : Bool
+case: the relative element (pronoun, relative pronoun) bears case marking for its role inside the RC. -case: no case-marked element in NP_rel (gap/deletion).
- su : Bool
- do_ : Bool
- io : Bool
- obl : Bool
- gen : Bool
- ocomp : 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.
- Phenomena.FillerGap.Studies.KeenanComrie1977.instBEqStrategyEntry.beq x✝¹ x✝ = false
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Which AH position does this strategy cover?
Equations
Instances For
List of AH positions covered by this strategy.
Equations
Instances For
Is this a primary strategy? Primary strategies cover subjects. HC₁ requires at least one primary strategy per language.
Instances For
HC₂: Does this strategy cover a contiguous segment of the AH?
Uses contiguousOnAH from Core.Relativization.Hierarchy, which mirrors
the contiguity check in Core.Case.Hierarchy.validInventory.
Equations
Instances For
Convert a fragment's RelClauseMarker to a Table 1 StrategyEntry.
The marker's bearsCaseMarking maps to ±case, and its positions
list determines per-position coverage.
Equations
- One or more equations did not get rendered due to their size.
Instances For
A language's full relativization profile from Table 1. Each language has one or more strategies covering (potentially overlapping) segments of the AH.
- language : String
- strategies : List StrategyEntry
- notes : String
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
HC₁: The language can relativize subjects (at least one strategy covers SU).
Equations
- p.satisfiesHC1 = p.strategies.any fun (x : Phenomena.FillerGap.Studies.KeenanComrie1977.StrategyEntry) => x.su
Instances For
HC₂: Every strategy covers a contiguous segment of the AH.
Equations
- p.satisfiesHC2 = p.strategies.all fun (x : Phenomena.FillerGap.Studies.KeenanComrie1977.StrategyEntry) => x.isContinuous
Instances For
PRC: Every primary strategy satisfies upward closure — if it covers position N, it covers all positions above N. This follows from HC₂ (contiguity) + isPrimary (covers SU at rank 6): a contiguous segment containing rank 6 and rank N must contain all intermediate ranks.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Build a KCProfile from a language name and its fragment marker list.
Equations
- One or more equations did not get rendered due to their size.
Instances For
English: two strategies derived from Fragments.English.relMarkers.
-case: complementizer that/∅, gap, covers SU/DO.
+case: relative pronoun who/whom/which/whose, covers IO–OCOMP.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Welsh: two strategies derived from Fragments.Welsh.relMarkers (§1.3.2).
-case: particle a, gap, covers SU/DO.
+case: particle y, resumptive pronoun, covers IO–OCOMP.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Arabic: two strategies derived from Fragments.Arabic.relMarkers (§1.3.2).
-case: alladhi, gap, covers SU only.
+case: resumptive pronoun, covers DO–OCOMP.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Hebrew: two strategies derived from Fragments.Hebrew.relMarkers (§1.3.2).
-case: complementizer she-, gap, covers SU/DO.
+case: she- + resumptive pronoun, covers DO–OCOMP.
DO is shared between both strategies.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Toba Batak: two strategies derived from Fragments.TobaBatak.relMarkers
(§1.3.2). -case: gap, covers SU only.
+case: resumptive pronoun, covers IO/OBL/GEN.
DO cannot be relativized by either strategy — a genuine gap.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Korean: two strategies derived from Fragments.Korean.relMarkers.
-case: adnominal suffix -(n)ɨn, -n, -l, gap, covers SU–OBL.
+case: genitive marker -uy, covers GEN only.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Finnish: two strategies derived from Fragments.Finnish.relMarkers.
+case: relative pronoun joka (declines for case), covers SU–GEN.
-case: prenominal participial, covers SU/DO.
OCOMP does not exist as a distinct category in Finnish.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Malagasy: one strategy derived from Fragments.Malagasy.relMarkers.
-case: gap, covers SU only. Voice alternation required for
non-subject relativization.
Equations
- One or more equations did not get rendered due to their size.
Instances For
All Table 1 profiles in our sample.
Equations
- One or more equations did not get rendered due to their size.
Instances For
HC₁ holds: every language in our sample can relativize subjects.
HC₂ holds: every strategy covers a contiguous segment of the AH.
PRC holds: every primary strategy satisfies upward closure.
The PRC follows from HC₂ for primary strategies: if a strategy is continuous and covers subjects (rank 6), then for any covered position at rank N, all positions with rank > N are also covered.
We verify this structural implication on all strategies in our sample: isPrimary ∧ isContinuous → upward-closed.
Every language has at least one primary strategy (restates HC₁ in terms of the StrategyEntry.isPrimary predicate).
In our sample, every -case strategy covers subjects. The -case (gap/deletion) strategy is always primary when present.
Multi-strategy languages: most languages in our sample use more than one strategy, with strategies covering different segments.
+case strategies that are non-primary (don't cover SU) never cover SU in our sample. This reflects the typological generalization that pronoun retention is used for lower, not higher, AH positions.
The gap-to-resumptive split: -case strategies always cover subjects, while +case secondary strategies never do. This means -case always occupies a strictly higher segment of the AH than non-primary +case.
Toba Batak has a genuine gap at DO: neither strategy can relativize direct objects. This is consistent with the HCs because each individual strategy is contiguous — the gap exists between strategies, not within one. The paper notes this explicitly.
Despite the DO gap, both of Toba Batak's individual strategies are contiguous (SU alone; IO–GEN alone). HC₂ is satisfied.
English covers all 6 AH positions across two strategies: -case (that/∅) covers SU/DO (2), +case (who/whom) covers IO–OCOMP (4).
Welsh splits at the DO/IO boundary: -case covers SU–DO, +case covers IO–OCOMP. Verified by checking coverage of each strategy.
Malagasy: single strategy, subject only.
Korean: -case strategy covers SU–OBL but not GEN.
Finnish: +case strategy is primary (covers SU) despite being +case. Finnish is an example where the +case strategy is the broader one.
Cross-reference: the Welsh WALS profile in Typology.lean records
lowestRelativizable := .oblique, but Table 1 shows the +case strategy
covers all the way to OCOMP. The discrepancy reflects that WALS
and Table 1 use different data sources and granularity — WALS Ch 123
only asks about obliques, not the full AH.
Sample size: 8 languages from Table 1.
Lowest AH position covered by any strategy in a KCProfile.
Returns the position with the smallest rank that is covered by
at least one strategy. Returns .subject if nothing else matches.
Equations
- One or more equations did not get rendered due to their size.
Instances For
English: KCProfile covers all 6 positions (lowestCovered = OCOMP),
matching Typology.english.lowestRelativizable = .objComparison.
Welsh: KCProfile covers down to OCOMP (via +case strategy),
though WALS records .oblique (Ch 123 only asks about obliques).
Korean: KCProfile covers SU-OBL + GEN, lowest = GEN.
WALS records .oblique (doesn't track GEN).
Malagasy: both systems agree — subjects only.
Finnish: KCProfile covers SU-GEN (via joka), WALS records .oblique.
Both agree that Finnish covers at least obliques.
Hebrew: KCProfile covers all positions via +case (DO-OCOMP).
WALS records .oblique.
Arabic: KCProfile covers all positions (SU via gap, DO-OCOMP via resumptive).
WALS records .oblique.
Systematic coverage agreement: for every language in our sample that also appears in the WALS typology, the KCProfile covers at least as much as the WALS profile indicates. The WALS profile never claims a language can relativize a position that Table 1 doesn't cover — Table 1 is strictly more detailed.