subsumes

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

A broader concept subsumes a narrower concept. Non-functional, not transitive at the core: a concept hierarchy may be polyhierarchical and source-specific, and any transitive closure is computed by the solver layer (Principle 12). The bridge to skos:broader is authored in the mapping DSL, not as an OWL axiom.

Structure

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

Practical Pattern

Use gmeow:subsumes from gmeow:Concept to gmeow:Concept when the relationship itself belongs in the native GMEOW graph.

Common Companion Terms

gmeow:Concept

External Equivalences

Equivalent or closely aligned targets: skos

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 assert a broader/narrower relation between two gmeow:Concept individuals when the concept structure itself is being modelled.

Avoid when

• Avoid declaring it transitive in OWL (transitive closure is solver work) and avoid asserting skos:broader as an axiom here; the skos mapping lives in the mapping DSL.

How to use

• Point the broader concept at the narrower concept; for SKOS exports, rely on the mapping projection.

Examples

• ex:animal gmeow:subsumes ex:mammal.