Core Ontology for Petroleum Installations · INF-UFRGS-Ontologies · CNPq INF-UFRGS-ENERGIA inf.ufrgs.br/ontologies/copi dee69df
exported necessary
pipe tee
IRI: http://www.inf.ufrgs.br/ontologies/copi#Pipetee
Generated on 2026-04-16
Natural Language Definition
EN
A pipe tee is a pipe fitting that has three fluid ports arranged in T-shaped configuration, with one branch port perpendicular to two run ports, designed to realize fluid conduction function through flow division or combination.
PT-BR
Um tê de tubulação é uma conexão de tubulação que possui três portas de fluido dispostas em configuração em formato de T, com uma porta de ramal perpendicular a duas portas de passagem, projetada para realizar função de condução de fluido através de divisão ou combinação de fluxo.
Formal Axioms
Semi-formal (Aristotelian)
Every pipe tee is a pipe that bears a fluid conduction function and has a branch port as a component part at all times.
First-Order Logic Theory
Loading…
▸ Stored override ∀x(PipeTee(x) → Pipe(x) ∧ ∃f(FluidConductionFunction(f) ∧ bearerOf(x,f)) ∧ ∃p(BranchPort(p) ∧ hasComponentPartAtAllTimes(x,p)))
OWL 2 / Turtle
@prefix copi: <https://www.inf.ufrgs.br/ontologies/copi/> . @prefix : <https://www.inf.ufrgs.br/ontologies/copi/> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix bfo: <http://purl.obolibrary.org/obo/> . @prefix iof-core: <https://spec.industrialontologies.org/ontology/construct/> . @prefix iof-av: <https://spec.industrialontologies.org/ontology/annotation/> . @prefix skos: <http://www.w3.org/2004/02/skos/core#> . @prefix qudt: <http://qudt.org/schema/qudt/> . @prefix dcterms: <http://purl.org/dc/terms/> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix apv: <http://inf.ufrgs.br/ontologies/apv#> . ### COPI — Core Ontology for Petroleum Installations ### Class module: PipeTee <https://www.inf.ufrgs.br/ontologies/copi> rdf:type owl:Ontology ; dcterms:title "Core Ontology for Petroleum Installations (COPI)"@en ; dcterms:title "Ontologia Core para Instalações de Petróleo (COPI)"@pt-br ; dcterms:description "BFO/IOF-Core conformant ontology of equipment classes for petroleum production plants, developed using the five-step RDL enrichment method."@en ; skos:scopeNote "Material artifacts (bfo:material_entity) that (i) are part of a petroleum production plant, and (ii) bear at least one function whose realization involves the transport (e.g. production and injection), processing (separation and other processes), control, monitoring, measurement, containment or offloading of material or energy."@en ; skos:scopeNote "Artefatos materiais (bfo:material_entity) que (i) fazem parte de uma planta de produção de petróleo, e (ii) possuem ao menos uma função cuja realização envolve o transporte (p. ex. produção e injeção), processamento (separação e outros processos), controle, monitoramento, medição, contenção ou escoamento de material ou energia."@pt-br ; skos:scopeNote "COPI provides high-level equipment categories defined by function to demonstrate the defined-class mechanism. Equipment subtypes are annotated with references to CFIHOS and PCA RDL terms. COPI is not a reference data library; organizations should use CFIHOS, PCA RDL, or ISO 14224 for comprehensive equipment classification."@en ; skos:scopeNote "COPI fornece categorias de alto nível de equipamentos definidas por função para demonstrar o mecanismo de classe definida. Os subtipos de equipamentos são anotados com referências aos termos do CFIHOS e do PCA RDL. COPI não é uma biblioteca de dados de referência; organizações devem utilizar o CFIHOS, o PCA RDL ou a ISO 14224 para classificação abrangente de equipamentos."@pt-br ; owl:versionInfo "1.1.0" ; owl:imports <https://spec.industrialontologies.org/ontology/core/Core/> ; owl:imports <http://purl.obolibrary.org/obo/bfo/2020/bfo.owl> ; dcterms:creator "Nicolau Oyhenard dos Santos"@en ; dcterms:contributor "Cauã Antunes" ; dcterms:contributor "Haroldo Rojas" ; dcterms:contributor "Rafael Petry" ; dcterms:contributor "Régis Romeu" ; dcterms:contributor "Mara Abel" ; dcterms:isPartOf <https://inf.ufrgs.br/projetos/OntoKG> ; dcterms:publisher "Universidade Federal do Rio Grande do Sul (UFRGS)"@en ; dcterms:license <https://creativecommons.org/licenses/by/4.0/> ; dcterms:created "2026-04-08"^^xsd:date ; dcterms:modified "2026-10-08"^^xsd:date ; apv:GlobalMinLanguageCoverage "en pt-br" ; apv:ClassURIFormationRule "https://www[.]inf[.]ufrgs[.]br/ontologies/copi/(COPI_[0-9]{7}|[A-Z][A-Za-z0-9]*)" ; apv:ClassMinAnnotationCoverage "rdfs:label https://spec.industrialontologies.org/ontology/annotation/naturalLanguageDefinition" . iof-av:naturalLanguageDefinition rdf:type owl:AnnotationProperty ; apv:MinAnnotationLength 20 . ### Identity-giving function :COPI_0000529 rdf:type owl:Class ; # FluidConductionFunction rdfs:subClassOf iof-core:DesignedFunction ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty bfo:BFO_0000054 ; # realizedIn owl:allValuesFrom :COPI_0000530 # FluidConductionProcess ] ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty bfo:BFO_0000054 ; # realizedIn owl:someValuesFrom :COPI_0000530 # FluidConductionProcess ] ; rdfs:label "fluid conduction function"@en ; rdfs:label "função de condução de fluido"@pt-br . ### Process type :COPI_0000530 rdf:type owl:Class ; # FluidConductionProcess rdfs:subClassOf :COPI_0000003 ; # MomentumTransfer rdfs:label "fluid conduction process"@en ; rdfs:label "processo de condução de fluido"@pt-br . :COPI_0000003 rdf:type owl:Class . # MomentumTransfer :COPI_0000530 # FluidConductionProcess rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasInput ; owl:someValuesFrom :COPI_0000037 # PortionOfFluid ] ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasSpecifiedOutput ; owl:someValuesFrom :COPI_0000037 # PortionOfFluid ] . ### Equipment universal: PipeTee :COPI_0000325 rdf:type owl:Class ; # PipeTee rdfs:subClassOf :COPI_0000321 ; # Pipe rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasFunction ; # Object branch (MaterialArtifact/Assembly/Object/FiatObjectPart) owl:someValuesFrom :COPI_0000529 # FluidConductionFunction ] ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasComponentPartAtAllTimes ; owl:someValuesFrom :COPI_0000424 # BranchPort ] ; rdfs:label "pipe tee"@en ; rdfs:label "tê de tubulação"@pt-br ; iof-av:naturalLanguageDefinition "A pipe tee is a pipe fitting that has three fluid ports arranged in T-shaped configuration, with one branch port perpendicular to two run ports, designed to realize fluid conduction function through flow division or combination."@en ; skos:definition "A pipe tee is a pipe fitting that has three fluid ports arranged in T-shaped configuration, with one branch port perpendicular to two run ports, designed to realize fluid conduction function through flow division or combination."@en ; iof-av:naturalLanguageDefinition "Um tê de tubulação é uma conexão de tubulação que possui três portas de fluido dispostas em configuração em formato de T, com uma porta de ramal perpendicular a duas portas de passagem, projetada para realizar função de condução de fluido através de divisão ou combinação de fluxo."@pt-br ; iof-av:semiFormalNaturalLanguageAxiom "Every pipe tee is a pipe that bears a fluid conduction function and has a branch port as a component part at all times."@en ; iof-av:firstOrderLogicAxiom "∀x(PipeTee(x) → Pipe(x) ∧ ∃f(FluidConductionFunction(f) ∧ bearerOf(x,f)) ∧ ∃p(BranchPort(p) ∧ hasComponentPartAtAllTimes(x,p)))"@en ; iof-av:isPrimitive "true"^^xsd:boolean ; iof-av:primitiveRationale "Using necessary conditions for this constructive type. The T-shaped geometric configuration with three specific ports is a structural differentia that is harder to make sufficient under OWA. Custom manifolds or complex fittings might contain T-shaped passages but should not be automatically classified as standard pipe tees without domain expert validation."@en ; skos:definition "[ISO 15926-4] A <PIPE TEE> is a <PIPING COMPONENT> and a <PIPING NETWORK NODE> and three piping ends in T-shape, including a branch at 90 degrees"@en ; skos:definition "[CFIHOS] A physical object that has three piping ends in T-shape, including a branch at 90 degrees."@en ; skos:definition "[POSC Caesar] An 'artefact' that has three piping ends in T-shape, including a branch at 90 degrees."@en . :COPI_0000424 rdf:type owl:Class ; # BranchPort rdfs:subClassOf :COPI_0000536 ; # FluidPort rdfs:label "bocal de ramal"@pt-br ; rdfs:label "branch port"@en . # Disjointness: PipeTee and PipeElbow [] rdf:type owl:AllDisjointClasses ; owl:members ( :COPI_0000325 :COPI_0000323 ) . # PipeTee, PipeElbow
Axiomatization Decision Log
1 Identity-Giving Function
Function class
FluidConductionFunction ⊑ DesignedFunction
Realized in
FluidConductionProcess ⊑ MomentumTransfer
Like other pipe fittings, the pipe tee's basic function is to conduct fluid while enabling flow division/combining. This is the same generic function as pipes and pipe elbows - it provides a conduit for fluid flow. The T-shape configuration enables branching but the identity-giving function is still fluid conduction.
2 Genus Determination
Pipe
A pipe tee is fundamentally a specialized form of pipe fitting that provides branching functionality. The source hierarchies suggest 'PIPING COMPONENT' but the most specific appropriate genus from our enriched classes is 'pipe', which captures that this is a fluid conduction artifact. Pipe tees are monolithic artifacts (typically cast or forged as a single piece) without removable subcomponents, making MaterialArtifact the appropriate BFO root rather than Assembly.
3 Necessary Parts
Part class Parent Relation
BranchPort FluidPort hasComponentPartAtAllTimes
The essential parts reflect the T-geometry: three ports (one branch, two run) and the body that houses the flow passages in T-configuration.
4 Process Participation Signature ⟨I, O, T⟩
Inputs (I)
PortionOfFluid — can enter through run port(s) or branch port
Outputs (O)
PortionOfFluid — exits through remaining port(s) - combining or dividing flow
Transformation (T)
flow division or flow combining - no phase change or chemical transformation
A pipe tee can operate in combining mode (two inlets, one outlet) or dividing mode (one inlet, two outlets), enabling fluid distribution or collection without altering the fluid properties.
5 Axiom Mode Decision

Necessary conditions only — modelled as a primitive universal (⊑, SubClassOf). Identity is grounded in designed function and cannot be reduced to a property checklist.

Using necessary conditions for this constructive type. The T-shaped geometric configuration with three specific ports is a structural differentia that is harder to make sufficient under OWA. Custom manifolds or complex fittings might contain T-shaped passages but should not be automatically classified as standard pipe tees without domain expert validation.
Disjointness Axioms
pipe elbow
C1: pipe elbow. Incompatible geometric configurations - T-shaped branching versus curved two-port flow path. Cannot have both three-port T-geometry and two-port curved geometry simultaneously.
Cross-Standard Observations
All three sources consistently define pipe tee by the same geometric criterion: three piping ends in T-shape with 90-degree branch. ISO15926 additionally classifies it as both PIPING COMPONENT and PIPING NETWORK NODE, emphasizing its structural and topological roles in piping systems.

Suggest a change

Opens a pre-filled GitHub issue on the COPI repo — nothing is sent until you submit it there.