C-Command & Binding Domains
Mechanistic pages often use "binding" for a pointer from a use site back to a source. Linguistic binding is narrower. It asks which noun phrases are licensed as antecedents for reflexives, pronouns, and names. The basic geometry is c-command: a node c-commands the material under its sister.
1. C-command is a tree relation
A node c-commands its sister and everything below that sister. In "John said Mary praised himself", John c-commands the embedded clause, but Mary c-commands the reflexive inside her local clause. Principle A requires a reflexive to have a local antecedent, so Mary is licensed and John is not.
2. Binding principles are local tests
Principle A says a reflexive needs a local binder. Principle B says an ordinary pronoun must be free in its local domain. Principle C says a name cannot be bound by a co-referring expression that c-commands it. The principles are not just labels; they change when an antecedent is dragged in or out of the local domain.
3. Islands block filler-gap dependencies
Filler-gap dependencies use similar geometry but a different constraint family. The gap can be linked to a displaced filler across ordinary clause boundaries, but not out of islands such as complex noun phrases or adjuncts. An island suite therefore tests whether a model is tracking structural boundaries rather than only linear distance.
- Binding for the mechanistic source/use/distractor framing.
- Dependency Trees & Structural Probes for dependency-depth and tree-distance readouts.
- Subspace Geometry for cross-model probe alignment.