Triple
T116980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pressure Vessels and Piping Division |
E2360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ASME division |
C1011
|
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: ASME division Context triple: [Pressure Vessels and Piping Division, instanceOf, ASME division]
-
A.
division of IEEE
A division of IEEE is a specialized organizational unit within the Institute of Electrical and Electronics Engineers that focuses on advancing a particular technical field or professional area through standards, publications, conferences, and member activities.
-
B.
division of a scientific society
chosen
A division of a scientific society is a specialized subunit within the society that focuses on a particular discipline, topic, or professional interest, organizing activities, research, and member services related to that area.
-
C.
academic division
An academic division is a major organizational unit within an educational institution that groups related departments, programs, or disciplines under a common administrative and academic structure.
-
D.
engineering journal
An engineering journal is a periodical publication that presents peer-reviewed research, technical developments, and practical applications in various fields of engineering.
-
E.
organizational unit of IEEE
An organizational unit of IEEE is a formally recognized group within the IEEE structure, such as a society, council, region, section, chapter, or committee, that carries out specific professional, technical, or administrative functions in support of IEEE’s mission.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.