Hopper

Definition & axiom

Label (EN)

hopper

Label (PT-BR)

Definition (EN)

Definition (PT-BR)

Semi-formal axiom (Aristotelian)

Axiom type

Necessary only (⊑) Necessary + sufficient (≡)

LLM classification basis: function-based → ≡

The concept is defined across multiple sources primarily by its intended function - storing and dispensing/dosing solids or additives. The conical shape is mentioned as a typical feature but the core identity is the storage-and-dispensing function, not the physical form.

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 SolidStorageAndDispensingFunction → SolidStorageAndDispensingProcess ⊑ MaterialContainment ▼

Function Class

Parent ↗ IOF-Core

Process Class

Process Parent ↗ IOF-Core

COPI-Core operation MaterialContainment via process parent MaterialContainment

LLM rationale: The identity-giving function combines storage of solid materials with controlled dispensing/dosing capability. This distinguishes hoppers from simple containers (which only store) and from feeders (which only dispense). The combination of temporary storage with controlled discharge is what makes a hopper a hopper.

▸ Expert review

2 Genus Proximus ✓ done Vessel · 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

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: The parent candidates include CONTAINER (iso15926), vessel (cfihos), and Artefact (posc_caesar). 'vessel' is the most specific appropriate superclass that is already enriched in our ontology. It represents the containment aspect while being more specific than the generic 'container' or 'artefact'. Vessels are typically assemblies with containment function, which aligns with hopper design.

▸ Expert review

3 Differentia Specifica ✓ done ∃bearerOf.SolidStorageAndDispensingFunction ⊓ ∃hasComponentPartAtAllTimes.SolidDischargeOpening ▼

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

Differentia expression

Differentia (natural language)

LLM rationale: The specific designed function for solid storage and dispensing is the primary differentia, along with the necessary discharge opening component that enables the dispensing capability. The conical shape mentioned in definitions is a typical but not universal feature.

▸ Expert review

4 Necessary Parts ✓ done no necessary parts ▼

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

LLM rationale: These parts are essential to the hopper's dual function of storage and controlled dispensing. The discharge opening enables the dispensing function while the storage compartment enables the storage function.

▸ Expert review

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

Inputs (I)

Outputs (O)

Transformation (T)

LLM rationale: Hoppers receive solid materials for storage and dispense the same materials in a controlled manner. No chemical transformation occurs, only controlled material handling and flow regulation.

▸ 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).

Properties as BFO qualities 0 of 6 selected ▼

Select which CFIHOS/DEXPI properties inhere in every instance of Hopper as bfo:Quality subclasses.

design specification Text

A specification according to which an item is intended to be designed

lower limit design temperature TEMP Number

The lowest temperature at which a functional or physical object is designed.

normal volume flow rate VOLFLO Number

A volume flow rate a functional or physical object is designed to deliver under normal conditions.

pressure equipment category Text

The pressure equipment category according to the pressure equipment directive 97/23/EC.

upper limit design pressure PRESS Number

The highest pressure at which a functional or physical object is designed for.

upper limit design temperature TEMP Number

The highest temperature at which a functional or physical object is designed.

Each selected property → :HopperQuality ⊑ bfo:Quality, inheres in :Hopper

Custom axioms none ▼

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

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)

iso15926 2019 ↗

HOPPER — ClassOfFunctionalObject