Triple
T18269954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulunsky District |
E437579
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of the Sakha Republic |
C15426
|
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: district of the Sakha Republic Context triple: [Bulunsky District, instanceOf, district of the Sakha Republic]
-
A.
autonomous okrug of Russia
An autonomous okrug of Russia is a type of federal subject with a degree of self-governance, typically established in areas with significant indigenous or ethnic minority populations and often administratively associated with a larger region or krai.
-
B.
district of Russia
chosen
A district of Russia is an administrative subdivision within a federal subject that manages local governance, public services, and regional implementation of national laws for its constituent settlements.
-
C.
district of Kaliningrad
A district of Kaliningrad is an administrative subdivision within the city of Kaliningrad, Russia, responsible for local governance, public services, and community infrastructure in its designated urban area.
-
D.
district of Ulaanbaatar
A district of Ulaanbaatar is an administrative subdivision of Mongolia’s capital city, responsible for local governance, public services, and community development within its designated urban area.
-
E.
economic region of Russia
An economic region of Russia is a territorial grouping of federal subjects organized for coordinated economic planning, development, and statistical analysis based on shared geographic, industrial, and infrastructural characteristics.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.