counterpart of

• CURIE: gmeow:counterpartOf
• IRI: https://blackcatinformatics.ca/gmeow/counterpartOf
• Category: property
• Defined by: gmeow:slices/coreference
• Box roles: RBox role (What is this?)

Relates two GMEOW entities that are recognisable counterparts across realms, frames, datasets, editions, or modelling contexts without being safely mergeable. Symmetric but deliberately not transitive: counterparts preserve cross-realm linkage while avoiding owl:sameAs collapse of contested, standpoint-indexed, or context-dependent claims.

Structure

Property shape: object property; gmeow:Entity -> gmeow:Entity

Practical Pattern

Use gmeow:counterpartOf from gmeow:Entity to gmeow:Entity when the relationship itself belongs in the native GMEOW graph.

Example Snippets

These snippets are generated from canonical slice examples and trimmed to the Turtle blocks where this term appears.

Authority Links

• Source: slices/core/coreference/examples/authority-links.ttl
• Examples catalog: open in catalog#example-slices-core-coreference-examples-authority-links

# --- A field-robot software identity that is the SAME agent across contexts as
#     the recorded author's account — a counterpart, not a sameAs merge.
ex:fieldRobotIdentity a gmeow:SoftwareAgent ;
    gmeow:name "lin-field-robot"@en ;
    gmeow:counterpartOf ex:recordedAuthor .

Common Companion Terms

gmeow:Entity

External Equivalences

Equivalent or closely aligned targets: prov

Linkages

Generated from the canonical mapping DSL. SSSOM files are the generated public interchange form for term equivalences.

Term Equivalences

Usage Advice

Use when

• Use to link two GMEOW entities that are the same thing across distinct realms, frames, datasets, or fictional/real boundaries — a fictional city and its real namesake, a record in two databases — while each keeps its own identity and context.

Avoid when

• Avoid for entity-to-external-record references (use gmeow:authorityLink) and for genuine mergers; never reach for owl:sameAs to collapse counterparts, since it is symmetric-only by design to keep contested or context-dependent claims standpoint-indexed rather than transitively identified.

How to use

• Assert gmeow:counterpartOf between the two GMEOW nodes in one direction and read it both ways; because it is intentionally non-transitive, state each pairing you mean and carry any disputed correspondence on the statement layer rather than chaining through a hub.

Examples

• ex:novelLondon gmeow:counterpartOf ex:realLondon.