Definition & axiom
⚠ Conflicts with the ISO 15926-4 primary definition
Label (EN)
pig trap
Label (PT-BR)
Definition (EN)
Definition (PT-BR)
Semi-formal axiom (Aristotelian)
Axiom type
LLM classification basis: function-based → ≡
The concept is defined by its identity-giving function of launching and receiving pipe pigs for pipeline maintenance operations. The structural configuration (launcher and receiver) serves to realize this function rather than being the primary basis for identity.
Validation status
Why primitive (necessary only)
Reviewer notes
FOL theory & disjointness
First-order logic theory (generated)
Loading…
Disjoint with
▸
Expert review
Axiomatization steps
1
Identity-Giving Function
✓ done
⚠ not anchored
PigLaunchingAndReceivingFunction → PigLaunchingAndReceivingProcess
▼
COPI-Core operation
⚠ Process parent
PlannedProcess reaches no COPI-Core operation, and no gap (out of scope / coverage gap) is recorded.
LLM rationale:
The identity-giving function is the capability to launch and receive pipe pigs for pipeline maintenance operations. This is what makes a pig trap distinct from other pipeline equipment - it enables the insertion and retrieval of cleaning, inspection, or maintenance devices into/from the pipeline.
▸
Expert review
2
Genus Proximus
✓ done
Assembly
▼
Genus (genus proximum)
Most specific superclass — may be a domain class like "Valve" or an IOF-Core root.
BFO/IOF-Core Root
bfo:Object branch
bfo:ObjectAggregate branch
bfo:ImmaterialEntity branch
LLM rationale:
No domain-specific parent candidates are appropriate. 'TOOL' is too general and 'piping and pipeline equipment' is not a formal ontological class. A pig trap is a complex mechanical assembly with launcher and receiver components that work together as a unified maintainable unit. It fits the Assembly pattern as a causally unified artifact with physically connected removable subcomponents.
▸
Expert review
3
Differentia Specifica
✓ done
∃bearerOf.PigLaunchingAndReceivingFunction ⊓ ∃hasComponentPartAtAllTimes.PigLauncher ⊓ ∃hasComponentPartAtAllTimes.PigReceiver
▼
Conditions that distinguish
Pig Trap
from sibling classes under genus
Assembly.
Only what is not already entailed by the genus.
Differentia expression
Differentia (natural language)
LLM rationale:
The functional differentia (pig launching/receiving function) combined with the structural differentia (having both launcher and receiver components) uniquely distinguishes pig traps from other pipeline assemblies. Both aspects are necessary as the function requires the specific dual-component structure.
▸
Expert review
4
Necessary Parts
✓ done
PigLauncher, PigReceiver
▼
Consider part-whole relations beyond subsumption:
hasComponentPartAtAllTimes (universal, structurally essential)
· hasComponentPartAtSomeTime (contingent, optional component)
LLM rationale:
These parts are constitutive of the pig trap's ability to perform its function. The launcher and receiver are definitional components, while closures are operationally necessary for safe pig handling.
▸
Expert review
5
Process Participation Signature ⟨I, O, T⟩
✓ done
⚠ 1 not in vocab
PortionOfFluid + PipelinePig → PortionOfFluid + PipelinePig
▼
⚠ Participant type(s) not in COPI vocabulary
PipelinePig(already published — grandfathered)
Participant types are hand-authored in
copi-vocab, not produced by the pipeline.
Replace each with an existing vocab type, redirect it to a BFO / IOF-Core class in copi-iri-map.tsv,
or add it to copi-vocab.ttl first.
Inputs (I)
Outputs (O)
Transformation (T)
LLM rationale:
The pig trap enables pig operations while maintaining pipeline flow continuity. The pig is inserted via launcher and retrieved via receiver while the process fluid continues flowing.
▸
Expert review
More
Alternative labels
none
▼
Synonyms / alternative labels (comma-separated) — skos:altLabel
Language auto-detected on export (PT if the label contains accents, EN otherwise).
Properties as BFO qualities
0 of 8 selected
▼
Select which CFIHOS/DEXPI properties inhere in every instance of Pig Trap as
bfo:Quality subclasses.
Each selected property →
:PigTrapQuality ⊑ bfo:Quality, inheres in :PigTrap
Custom axioms
none
▼
Axioms not produced by the pipeline. Each is appended verbatim as an
rdfs:subClassOf restriction on Pig Trap.
Write the restriction block in Turtle syntax (without the leading
rdfs:subClassOf).
Example: [ owl:onProperty :hasPart ; owl:someValuesFrom :Wellhead ]
Cross-standard divergences
none detected yet
▼
Click "Detect divergences" to analyse cross-standard disagreements for this cluster.
