Triple
T9166584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagorno-Karabakh Autonomous Oblast |
E219975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous oblast |
C25746
|
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 oblast Context triple: [Nagorno-Karabakh Autonomous Oblast, instanceOf, autonomous oblast]
-
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.
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.
-
C.
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.
-
D.
non-self-governing territory
A non-self-governing territory is a geographic area under the administrative control of another state where the local population has not yet achieved full self-government or independence.
-
E.
autonomous region of China
An autonomous region of China is a first-level administrative division granted a degree of self-governance and cultural autonomy, typically in areas with significant ethnic minority populations.
- F. None of above. chosen
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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:22 p.m.