Triple
T21139702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toponymy Commission |
E520898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | linguistic standardization body |
C19550
|
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: linguistic standardization body Context triple: [Toponymy Commission, instanceOf, linguistic standardization body]
-
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.
linguistic organization
chosen
A linguistic organization is an entity that systematically studies, regulates, promotes, or supports the use, development, and preservation of languages and linguistic practices.
-
C.
standardized language variety
A standardized language variety is a codified form of a language that has been deliberately regulated and accepted as the norm for public, official, and educational use within a speech community.
-
D.
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.
-
E.
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.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:57 p.m.