Triple
T116769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASME Boiler and Pressure Vessel Code |
E2355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering standard |
C2538
|
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: engineering standard Context triple: [ASME Boiler and Pressure Vessel Code, instanceOf, engineering standard]
-
A.
engineering journal
An engineering journal is a periodical publication that presents peer-reviewed research, technical developments, and practical applications in various fields of engineering.
-
B.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
C.
civil engineer
A civil engineer is a professional who designs, constructs, and maintains infrastructure projects such as roads, bridges, buildings, and water systems to ensure safety, functionality, and sustainability.
-
D.
engineering firm
An engineering firm is a business organization that provides professional engineering services—such as design, analysis, consulting, and project management—to plan, develop, and implement technical solutions for clients in various industries.
-
E.
technical standards body
A technical standards body is an organization that develops, maintains, and promotes agreed-upon technical specifications and protocols to ensure interoperability, safety, and consistency across industries and technologies.
- F. None of above. chosen
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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.