Triple
T26427264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPARQL Working Group |
E664402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Standards body |
C3871
|
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: Standards body Context triple: [SPARQL Working Group, instanceOf, Standards body]
-
A.
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.
-
B.
standards-setting organization
chosen
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.
-
C.
standards oversight body
A standards oversight body is an organization responsible for developing, maintaining, and enforcing technical or procedural standards to ensure consistency, quality, and interoperability across a domain.
-
D.
organ of the International Organization for Standardization
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.
certification body
A certification body is an independent organization that assesses and verifies whether products, services, systems, or individuals meet specified standards or requirements, and issues formal certificates to confirm compliance.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:46 p.m.