Case grammar¶

A linguistic analysis in which a predicate selects a case frame of semantic roles that its participants fill beneath their surface syntactic realization.

Version: v2 · 2026-09-19 · History
Domain-specific #: 3601
Domain group: Humanities
Origin domain: Linguistics & Semiotics
Subdomain: Linguistic Theory → Linguistics & Semiotics

Core Idea¶

Deep cases are semantic roles rather than morphological case endings, inventories differ across formulations and the same role may surface through different grammatical constructions.^[1] A verb or other predicate specifies a valency frame of roles such as Agent, Object, Instrument or Beneficiary, and transformations map those role-bearing participants into surface clauses. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of linguistic theory. It is the domain-specific identity fixed by the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test. This gives the entry an operational identity rather than merely a historical label.

A useful analysis keeps three layers separate. The constitutive layer says what must be true: the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit. The evidential layer asks what observation or proof warrants the claim: type the carrier, state every parameter and convention in the definition, test that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. The use layer asks what reasoning becomes available once the identity is established: recognizing and comparing instances of Case grammar, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Conflating the layers is the most common source of scope inflation.

How would you explain it like I'm…

Who Does What With What

In 'Sam broke the window with a rock,' Sam is the one doing it, the window is what gets broken, and the rock is the tool. Case grammar says every action word comes with a set of jobs like doer, thing, and tool. The jobs stay the same even when you say the sentence differently, like 'The rock broke the window,' where the rock is still the tool.

The Roles a Verb Needs

Case grammar is a way of studying sentences by looking at the roles that people and things play in an action. A verb like 'open' comes with a set of roles, like who does it (the Agent), what gets opened (the Object), and what you use (the Instrument). The same role can show up in different spots in a sentence: 'Sam opened the door with a key' and 'The key opened the door' both have a key as the Instrument. These roles are about meaning, not about the word endings some languages use, which are also called 'cases'. Different linguists have made slightly different lists of these roles.

Semantic-Role Case Frames

Case grammar is a linguistic theory in which verbs and other predicates specify a case frame: a set of semantic roles, called deep cases, that their participants play, such as Agent, Object, Instrument or Beneficiary. These deep cases are about meaning, not the grammatical case endings some languages put on nouns. The theory says sentences are formed by taking these role-bearing participants and mapping them, through transformations, into surface positions like subject and object. So the same role can appear in different grammatical forms, as when an Instrument appears either as the subject or in a 'with' phrase. Different versions of the theory use different lists of roles, so an analysis must say which version it follows.

Case grammar is a framework in which a verb or other predicate, in a given lexical sense, specifies a valency frame of semantic roles, deep cases, such as Agent, Object, Instrument, and Beneficiary, that its participants bear. Deep cases are semantic roles rather than morphological case endings, and the inventory of roles differs among formulations of the theory. The case frame states which roles are required and which are optional, and imposes constraints on which roles can co-occur. Transformations then map the role-bearing participants onto surface clause structure as subjects, objects, obliques, or adjuncts, so the same role may surface through different grammatical constructions, as in alternations where an Instrument appears as subject. A proper case-grammar analysis therefore specifies the predicate and its sense, the participant inventory, the named roles, valency and optionality, co-occurrence constraints, the mapping to surface arguments and adjuncts, the treatment of alternations, and the theoretical version adopted. Treating deep cases as morphological cases, or as a fixed universal list, misreads the theory.

Structural Signature¶

Carrier: the typed linguistic theory carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets
Inputs or antecedent state: the exact linguistic theory carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Case grammar
Constitutive operation: A verb or other predicate specifies a valency frame of roles such as Agent, Object, Instrument or Beneficiary, and transformations map those role-bearing participants into surface clauses.
Invariant: the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit
Recognition test: type the carrier, state every parameter and convention in the definition, test that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases
Output or consequence: recognizing and comparing instances of Case grammar, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions
Failure boundary: the carrier is mistyped, the condition that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test

What It Is Not¶

It is not the whole field of linguistic theory. The field contains many questions and methods that do not instantiate Case grammar.
It is not its most familiar example. A canonical instance directly demonstrates that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit. exhibits the structure, but the example is evidence for the abstraction rather than its definition.
It is not the neighboring catalog concept Dependency grammar. Dependency grammar represents syntactic head-dependent structure; case grammar organizes the predicate’s underlying semantic-role frame and its surface realization.
It is not a claim that every boundary case has one uncontested classification. a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Case grammar must control the decision
It is not an unrestricted metaphor for any process that seems similar. Outside linguistic theory, the vocabulary and validity conditions do not transfer literally.

Scope of Application¶

Case grammar belongs to linguistic theory and is useful where the analyst can specify the typed linguistic theory carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit. The scope is broad within that domain but bounded by the need for the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.^[2]

Definition and recognition. Determine whether a proposed instance satisfies the constitutive conditions rather than merely sharing terminology.
Construction or evolution. Track how the exact linguistic theory carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Case grammar are converted, constrained, or organized by A verb or other predicate specifies a valency frame of roles such as Agent, Object, Instrument or Beneficiary, and transformations map those role-bearing participants into surface clauses..
Comparison. Compare instances using carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior, without treating convenience measures as the definition.
Boundary analysis. Diagnose cases where a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Case grammar must control the decision and state which convention or theorem controls the decision.
Downstream reasoning. Use the established identity to support recognizing and comparing instances of Case grammar, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions while preserving the assumptions under which the inference is valid.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Case grammar can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated. The disciplined statement is: given the exact linguistic theory carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Case grammar, the structure counts as Case grammar exactly when the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit.

This format also separates identity from measurement. Empirical, computational, or documentary proxies support recognition only under declared validity and uncertainty assumptions; formal cases require proof rather than measurement. Measurements can be noisy, implementations can approximate, and proofs can use equivalent characterizations; none of those facts licenses changing the object being measured. When reports disagree, first check scope and convention, then data or proof, and only then interpret the disagreement as substantive.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Case grammar. Case grammar compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

The compression has a price. A single label can hide canonical, generalized, restricted, approximate, computational, empirical, and historically variant formulations of Case grammar. Good use therefore carries a small declaration of assumptions alongside the name. The abstraction manages complexity when it reduces the state space of the question while keeping the failure boundary visible; it mismanages complexity when the label substitutes for that boundary analysis.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed linguistic theory carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit independently of one notation or implementation. This step prevents the canonical example from becoming the definition.
Derive consequences. From the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit, infer recognizing and comparing instances of Case grammar, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Record each assumption used so that a later change of setting does not silently preserve an invalid conclusion.
Test adversarial cases. Examine a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Case grammar must control the decision and an object that resembles Case grammar in purpose or vocabulary but does not satisfy its invariant is outside the class. A robust identity explains why the first is convention-sensitive and why the second is outside the class.
Compare and refine. Use carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior to compare legitimate instances, and refine the model when discrepancies reflect hidden variation rather than failure of the abstraction itself.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of linguistic theory because they reuse the typed linguistic theory carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, A verb or other predicate specifies a valency frame of roles such as Agent, Object, Instrument or Beneficiary, and transformations map those role-bearing participants into surface clauses., and type the carrier, state every parameter and convention in the definition, test that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. A theorem, diagnostic, or modeling warning can travel when those roles remain literal. For example, the distinction between constitutive identity and a convenient observable transfers from A canonical instance directly demonstrates that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit. to An applied instance preserves the invariant under changed notation, scale, dataset, jurisdiction, or implementation..^[n1]

Transfer outside the home domain is weaker. The skeletal pattern—type the carrier, apply the defining mechanism of Case grammar, preserve its invariant, and derive only consequences licensed by the stated boundary—may suggest an analogy, but the domain-specific mechanisms, admissible evidence, and consequences do not come along automatically. The safe transfer procedure maps each role explicitly, checks the invariant again, and refuses the name when only a superficial resemblance remains.

Examples¶

Canonical¶

A canonical instance directly demonstrates that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit. The example exposes the carrier and directly tests that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit; changing incidental notation preserves the identity, while removing that condition destroys it. This example is canonical because every role can be inspected: the carrier is the typed linguistic theory carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets; the operative rule is A verb or other predicate specifies a valency frame of roles such as Agent, Object, Instrument or Beneficiary, and transformations map those role-bearing participants into surface clauses.; the invariant is the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit; and the result supports recognizing and comparing instances of Case grammar, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions.^[1] Changing incidental notation or scale leaves the structure intact, while removing the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit destroys the classification.

Mapped back: the typed linguistic theory carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets → A verb or other predicate specifies a valency frame of roles such as Agent, Object, Instrument or Beneficiary, and transformations map those role-bearing participants into surface clauses. → the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit → recognizing and comparing instances of Case grammar, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions

Applied / In Practice¶

An applied instance preserves the invariant under changed notation, scale, dataset, jurisdiction, or implementation. The applied case qualifies only because the same invariant and boundary test remain literal under changed parameters or implementation. The applied case is not licensed merely by vocabulary. It qualifies because the same recognition test—type the carrier, state every parameter and convention in the definition, test that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases—can be run and because the same failure boundary—the carrier is mistyped, the condition that the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version are explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test—remains meaningful.^[2] The case also shows why practical outputs should report assumptions, resolution, and uncertainty instead of a naked label.

Mapped back: declared instance → recognition test → boundary check → qualified use

Structural Tensions¶

T1: Axiomatic identity vs. operational recognition. The defining conditions may be exact while empirical or computational recognition is approximate. Neither pole can be removed without changing the analytical task. Diagnostic: Can the reviewer state both the exact condition and the evidence used to infer it?
T2: Local roles vs. global consequence. The mechanism is enacted through local relations, but the abstraction is usually valued for a global classification or prediction. Neither pole can be removed without changing the analytical task. Diagnostic: Does the claimed global result actually follow from the declared local conditions?
T3: Ideal form vs. finite representation. Theory states a clean invariant while data structures, measurements, or proofs expose only finite representations. Neither pole can be removed without changing the analytical task. Diagnostic: Would increasing resolution converge toward the same classification?
T4: Canonical convention vs. legitimate variants. A standard formulation supports communication, while variants may preserve the same core under changed assumptions. Neither pole can be removed without changing the analytical task. Diagnostic: Which role is invariant across variants, and which convention-specific conclusion changes?
T5: Compression vs. hidden assumptions. The name compresses a complex argument but can conceal prerequisites. Neither pole can be removed without changing the analytical task. Diagnostic: Can each downstream inference be traced to an explicit assumption?
T6: Autonomous residual vs. reduction to catalog neighbors. The candidate uses broader structures but adds an identity-bearing residual. Neither pole can be removed without changing the analytical task. Diagnostic: After subtracting the proposed parent and named neighbors, does the constitutive residual still support independent diagnostics?

Structural–Framed Character¶

The entry is structurally mixed but domain-framed. Its portable skeleton is type the carrier, apply the defining mechanism of Case grammar, preserve its invariant, and derive only consequences licensed by the stated boundary. Its identity-bearing terms—Case grammar, carrier, parameter, invariant, boundary, evidence, model, transformation, and application—derive their meaning from linguistic theory and cannot be replaced by generic systems language without losing the tests that distinguish valid from invalid instances.

This mixed character explains why the abstraction is reusable inside the domain yet does not meet the Prime bar. The structure organizes reasoning, but its claims still depend on domain-specific objects, evidence, and intervention semantics.

Structural Core vs. Domain Accent¶

The structural core consists of a carrier, A verb or other predicate specifies a valency frame of roles such as Agent, Object, Instrument or Beneficiary, and transformations map those role-bearing participants into surface clauses., a recognition invariant, and a consequence. That skeleton may resemble patterns elsewhere, especially type the carrier, apply the defining mechanism of Case grammar, preserve its invariant, and derive only consequences licensed by the stated boundary. The domain accent is not decorative: Case grammar, carrier, parameter, invariant, boundary, evidence, model, transformation, and application determine what counts as an admissible carrier, a valid transition, and successful evidence.

The abstraction therefore remains domain-specific. A cross-domain reuse that preserves only words such as 'balance,' 'cut,' 'sequence,' 'loss,' or 'simulation' is metaphor. Literal transfer requires the original role structure and diagnostics, which in this case remain anchored in linguistic theory.

This entry is a kind of Relation.

It remains its own entry because its identity is fixed by the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version.

Relationships to Other Abstractions¶

Current abstraction Case grammar Domain-specific

Parents (1) — outgoing typed relations

Case grammar is a kind of Relation Prime

It remains its own entry because its identity is fixed by the predicate and lexical sense, participant inventory, named semantic roles, case-frame valency and optionality, constraints on role co-occurrence, mapping to surface arguments and adjuncts, treatment of alternations and the adopted theoretical version.

Hierarchy path (1) — routes to 1 parentless root

Case grammar → is a kind of Relation

Neighborhood in Abstraction Space¶

Case grammar sits in a crowded region of the domain-specific corpus (5^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Syntax, Semantics & Grammar Theory (24 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25

Not to Be Confused With¶

Dependency grammar. Dependency grammar represents syntactic head-dependent structure; case grammar organizes the predicate’s underlying semantic-role frame and its surface realization.
One canonical example. An instance demonstrates the structure but does not define the whole abstraction.
Measurement or implementation of Case grammar. A proxy or realization is evidence for the abstraction, not the abstraction itself.
Generalized Case grammar. An extension qualifies only when its changed axioms and retained invariant are stated.

Notes¶

[n1] Harold L. Somers, Valency and Case in Computational Linguistics, Edinburgh University Press. ↩

References¶

[1] Charles J. Fillmore, The Case for Case, in Universals in Linguistic Theory, 1968. registry ↩a ↩b

[2] Charles J. Fillmore, The Case for Case Reopened, in Syntax and Semantics 8, 1977. doi.orgnot authoritative registry ↩a ↩b