Triple
T23071812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTD |
E575216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ASME technical division |
C10849
|
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 technical division Context triple: [RTD, instanceOf, ASME technical division]
-
A.
ASME committee
chosen
An ASME committee is a formal group of experts and stakeholders organized by the American Society of Mechanical Engineers to develop, review, and maintain technical standards, codes, and guidelines in specific areas of mechanical engineering.
-
B.
program of the American Society of Mechanical Engineers
A program of the American Society of Mechanical Engineers is an organized set of activities, initiatives, or services designed to advance mechanical engineering knowledge, practice, standards, and professional development for its members and the broader engineering community.
-
C.
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.
-
D.
engineering division
The engineering division is an organizational unit responsible for designing, developing, and maintaining technical systems, products, and infrastructure within a company or institution.
-
E.
SAE International committee
A SAE International committee is a specialized group of experts organized under SAE International to develop, review, and maintain technical standards and guidelines for mobility engineering and related industries.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:56 p.m.