Triple
T8741881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamalo-Nenets Autonomous Okrug |
E207521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous okrug |
C5510
|
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: autonomous okrug Context triple: [Yamalo-Nenets Autonomous Okrug, instanceOf, autonomous okrug]
-
A.
autonomous okrug of Russia
chosen
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.
autonomous prefecture
An autonomous prefecture is an administrative division granted a degree of self-governance, typically to recognize and accommodate the political, cultural, and linguistic rights of a specific ethnic or regional minority group within a larger state.
-
C.
special autonomous region
A special autonomous region is a subnational territorial unit granted a high degree of self-governance and legislative autonomy distinct from other administrative divisions within the same country.
-
D.
district of Russia
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.
-
E.
федеральный округ России
Федеральный округ России — это укрупнённая административно-территориальная единица, объединяющая несколько субъектов Российской Федерации для обеспечения эффективного федерального управления и координации деятельности органов власти.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.