Triple
T26187750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khasi Hills Autonomous District Council |
E654876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous district council |
C51209
|
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 district council Context triple: [Khasi Hills Autonomous District Council, instanceOf, autonomous district council]
-
A.
autonomous area
An autonomous area is a geographically defined region that possesses a degree of self-governance and decision-making authority independent from the central governing body.
-
B.
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.
-
C.
autonomous county
An autonomous county is a county-level administrative division granted a degree of self-governance, often to recognize and accommodate the political, cultural, or ethnic distinctiveness of its local population.
-
D.
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.
-
E.
autonomous city government
An autonomous city government is a self-governing municipal authority that exercises significant political, administrative, and fiscal control over local affairs independent of higher levels of government.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:43 p.m.