Triple
T29399334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grinnell |
E745590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mechanical piping brand |
C39952
|
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: mechanical piping brand Context triple: [Grinnell, instanceOf, mechanical piping brand]
-
A.
piping standard
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.
-
B.
building material brand
A building material brand represents a company or label under which construction products and materials are marketed, recognized, and trusted for specific performance, quality, and aesthetic attributes in the building industry.
-
C.
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.
-
D.
industrial brand
chosen
An industrial brand is a business identity focused on products, services, and solutions sold to other organizations in industrial markets, emphasizing reliability, performance, and technical expertise.
-
E.
circuit protection brand
A circuit protection brand is a company or label that designs, manufactures, and markets devices and systems that prevent electrical circuits from damage due to overloads, short circuits, surges, or other electrical faults.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:49 p.m.