Triple
T8877495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bodoland Territorial Region |
E211323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous administrative division |
C740
|
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 administrative division Context triple: [Bodoland Territorial Region, instanceOf, autonomous administrative division]
-
A.
special administrative division
A special administrative division is a distinct territorial unit within a country that has unique legal, political, or administrative status differing from that of regular administrative regions.
-
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.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
E.
autonomous community government
An autonomous community government is a regional governing body with constitutionally recognized self-governing powers to manage political, administrative, and fiscal affairs within its territory under a broader national framework.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:52 p.m.