Skip to content

Type–Token Distinction

Origin domain
Philosophy Logic
Subdomain
ontology and semiotics → Philosophy Logic
Aliases
Type Token, Class Instance Distinction, Universal Particular Instantiation
Related primes
Abstraction

Core Idea

The type–token distinction separates a repeatable kind, pattern, symbol, or specification from its numerically distinct occurrences. Properties shared by all occurrences attach to the type; location, history, state, and identity particular to one occurrence attach to its token. A repeatable form, at least one occurrence, a membership or realization relation, and two levels of predication are required. Two tokens can be qualitatively identical while remaining numerically distinct.

Broad Use

Words and inscriptions, scores and performances, software classes and objects, designs and manufactured units, diseases and cases, and messages and transmissions preserve the distinction without translation.

Clarity

Class–instance is a formal-system specialization. Universal– particular adds metaphysical commitments not required here. Template instantiation is a production operation. Copy–original distinguishes historical lineage among tokens, not type from occurrence.

Manages Complexity

The abstraction turns a scattered family of cases into one role-based test: identify the required elements, test their relation, and reject the classification when a constitutive commitment is missing.

Abstract Reasoning

Use the structural signature rather than the label, then challenge the nearest counterexample. Saying that the letter “A” appears three times refers to one type and three tokens; treating the three marks as one physical object collapses the levels.

Knowledge Transfer

Words and inscriptions, scores and performances, software classes and objects, designs and manufactured units, diseases and cases, and messages and transmissions preserve the distinction without translation.

Example

A case qualifies only when the definition and every load-bearing role remain present. Saying that the letter “A” appears three times refers to one type and three tokens; treating the three marks as one physical object collapses the levels.

Relationships to Other Abstractions

Local relationship map for Type–Token DistinctionParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Type–TokenDistinctionPRIMEPrime abstraction: Abstraction — presupposesAbstractionPRIMEDomain-specific abstraction: Item (Copy) — is a decomposition ofItem (Copy)DOMAINPrime abstraction: Abstract Work — is a kind ofAbstract WorkPRIME

Current abstraction Type–Token Distinction Prime

Parents (1) — more general patterns this builds on

  • Type–Token Distinction presupposes Abstraction Prime

    Recognizing a repeatable type presupposes abstracting away token-specific location, time, state, and history while retaining the structure shared by its occurrences.

Children (2) — more specific cases that build on this

  • Abstract Work Prime is a kind of Type–Token Distinction

    Abstract Work is the enriched work-and-carrier species of the bare type-and-token split, adding a content identity criterion, attribution, and lineage.

  • Item (Copy) Domain-specific is a decomposition of Type–Token Distinction

    Removing the child’s frame leaves the reusable structure named by Type Token Distinction.

Hierarchy path (1) — routes to 1 parentless root

Not to Be Confused With

Class–instance is a formal-system specialization. Universal– particular adds metaphysical commitments not required here. Template instantiation is a production operation. Copy–original distinguishes historical lineage among tokens, not type from occurrence.

Notes

(Canonical first draft; queued for Claude house-style re-authoring and citation review.)