Triple
T27072981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabha Hasong Autonomous Council |
E685378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous 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 council Context triple: [Rabha Hasong Autonomous Council, instanceOf, autonomous council]
-
A.
autonomous district council
chosen
An autonomous district council is a local self-governing body in a specific district that exercises legislative, executive, and financial powers over designated subjects to preserve regional autonomy, culture, and development.
-
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 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.
-
D.
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.
-
E.
autonomous oblast
An autonomous oblast is a type of administrative division within a country that possesses a degree of self-governance and cultural or political autonomy, typically established to recognize and accommodate a specific ethnic or regional group.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:29 a.m.