Triple
T1510102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASME B31.12 Hydrogen Piping and Pipelines |
E33994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hydrogen piping code |
C1202
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: hydrogen piping code Context triple: [ASME B31.12 Hydrogen Piping and Pipelines, instanceOf, hydrogen piping code]
-
A.
pressure piping code
A pressure piping code is a set of engineering standards and regulations that govern the design, fabrication, inspection, testing, and operation of piping systems that contain fluids under pressure to ensure safety and reliability.
-
B.
piping standard
chosen
A piping standard is a formal specification that defines the materials, dimensions, design, fabrication, testing, and installation requirements for piping systems to ensure safety, compatibility, and performance.
-
C.
pressure equipment code
A pressure equipment code is a formal set of engineering standards and regulatory requirements that govern the design, fabrication, inspection, testing, and safe operation of pressure-containing equipment such as boilers, pressure vessels, and piping systems.
-
D.
pressure equipment
Pressure equipment comprises vessels, piping, and related components designed to contain, control, or transfer fluids under internal or external pressure safely and reliably.
-
E.
crane and hoist safety code
A crane and hoist safety code is a set of standardized rules and guidelines that govern the safe design, installation, operation, inspection, and maintenance of cranes and hoisting equipment to prevent accidents and ensure worker safety.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:24 p.m.