Triple
T1702720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principles, Policies, and Procedures for Domestic Geographic Names |
E36803
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | standard for geographic names |
C2077
|
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: standard for geographic names Context triple: [Principles, Policies, and Procedures for Domestic Geographic Names, instanceOf, standard for geographic names]
-
A.
geographical names authority
chosen
A geographical names authority is an entity or system responsible for standardizing, maintaining, and providing authoritative information on the official names and spellings of geographic places.
-
B.
informal geographic name
An informal geographic name is a non-official, commonly used label for a place or region that may not appear in formal records or maps but is widely recognized in everyday language.
-
C.
geographic markup language
Geographic Markup Language is an XML-based standard for encoding, storing, and exchanging geographic information and spatial features on the web.
-
D.
geographic code
A geographic code is a standardized alphanumeric identifier used to represent specific geographic areas or locations for purposes such as mapping, analysis, and data organization.
-
E.
historical place name
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.