Ball Valve

Definition & axiom

Label (EN)

ball valve

Label (PT-BR)

Definition (EN)

Definition (PT-BR)

Semi-formal axiom (Aristotelian)

Axiom type

Necessary only (⊑) Necessary + sufficient (≡)

LLM classification basis: structure-based → ⊑

Ball valve identity is primarily determined by its physical mechanism - a spherical ball closure member that rotates 90 degrees to control flow. All definitions emphasize the ball structure and rotation mechanism rather than a unique function distinct from other valve types. The function is the generic valve function of flow control.

Validation status

Why primitive (necessary only)

Reviewer notes

FOL theory & disjointness

First-order logic theory (generated)

                                  Loading…
                                

Disjoint with

▸ Expert review — accepted

Axiomatization steps

1 Identity-Giving Function ✓ done FlowControlFunction → FlowControlProcess ⊑ FlowControl ▼

Function Class

Parent ↗ IOF-Core

Process Class

Process Parent ↗ IOF-Core

COPI-Core operation FlowControl via process parent FlowControl

LLM rationale: Ball valves share the same identity-giving function as other valves - controlling fluid flow. This function is already established for the Valve class in our ontology. The ball mechanism is the differentiating factor, not a unique function.

▸ Expert review — accepted

2 Genus Proximus ✓ done Valve · MaterialArtifact ▼

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

Assembly ↗

Disassemblable unit (pump, compressor, HX)

MaterialArtifact ↗

Monolithic artefact (valve, pipe, sensor)

Object ↗

bfo:Object — when neither Assembly nor MaterialArtifact fits

FiatObjectPart ↗

Fiat part (well interval, pipe segment)

bfo:ObjectAggregate branch

EngineeredSystem ↗

Deliberate system of interacting objects (train, package)

ObjectAggregate ↗

bfo:ObjectAggregate — when EngineeredSystem is too specific

bfo:ImmaterialEntity branch

Site ↗

bfo:Site — cavity / spatial region (wellbore, annulus). No DesignedFunction axiom.

LLM rationale: All sources consistently identify ball valve as a subtype of valve (rotary valve, valve). Valve is already enriched in our ontology with FlowControlFunction. MaterialArtifact is appropriate as ball valves are causally unified artifacts that can be monolithic or have connected components maintained as single units.

▸ Expert review — accepted

3 Differentia Specifica ✓ done ∃hasComponentPartAtAllTimes.BallClosure ⊓ ∃participatesIn.RotationalMotionProcess ▼

Conditions that distinguish Ball Valve from sibling classes under genus Valve. Only what is not already entailed by the genus.

Differentia expression

Differentia (natural language)

LLM rationale: The ball closure member is the essential structural component that defines ball valve identity across all sources. The 90-degree rotational motion is the kinematic signature that distinguishes it from linear motion valves (gate) or other rotational designs (butterfly disc).

▸ Expert review — accepted

4 Necessary Parts ✓ done BallValveClosureMember ▼

Consider part-whole relations beyond subsumption: hasComponentPartAtAllTimes (universal, structurally essential) · hasComponentPartAtSomeTime (contingent, optional component)

LLM rationale: These are the minimal components that every ball valve must have: the ball itself, stem for actuation, and seat for sealing. Other components like actuators, bonnets vary by subtype.

▸ Expert review — accepted

5 Process Participation Signature ⟨I, O, T⟩ ✓ done PortionOfFluid → PortionOfFluid ▼

Inputs (I)

Outputs (O)

Transformation (T)

LLM rationale: Ball valves provide on-off or throttling control of single fluid streams through rotational positioning of the ball's flow passage

▸ Expert review

Alternative labels none ▼

Synonyms / alternative labels (comma-separated) — skos:altLabel

Language auto-detected on export (PT if the label contains accents, EN otherwise).

Custom axioms none ▼

Axioms not produced by the pipeline. Each is appended verbatim as an rdfs:subClassOf restriction on Ball Valve.

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 ▼

Full matrix

Click "Detect divergences" to analyse cross-standard disagreements for this cluster.

Source Definitions (5)