Triple
T3370917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO technical committee |
E70951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | standardization committee |
C5531
|
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: standardization committee Context triple: [ISO technical committee, instanceOf, standardization committee]
-
A.
standards-setting organization
A standards-setting organization is an entity that develops, maintains, and promotes agreed-upon technical, professional, or procedural norms to ensure compatibility, quality, and interoperability across industries or sectors.
-
B.
rule‑making committee
A rule‑making committee is a group formally tasked with developing, reviewing, and approving rules or regulations that govern the behavior, procedures, or operations of an organization or system.
-
C.
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.
-
D.
organ of the International Organization for Standardization
chosen
An organ of the International Organization for Standardization is a formal structural body within ISO, such as a council, committee, or technical group, that is responsible for specific governance, coordination, or standardization functions.
-
E.
ASME committee
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.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:13 p.m.