Triple
T26187751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khasi Hills Autonomous District Council |
E654876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local self-governing body |
C172
|
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: local self-governing body Context triple: [Khasi Hills Autonomous District Council, instanceOf, local self-governing body]
-
A.
self-governing organization
A self-governing organization is an entity that independently establishes and enforces its own rules, structures, and decision-making processes without external control.
-
B.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
C.
local organ of state power
A local organ of state power is a governmental body operating at the subnational level that exercises state authority and administers public affairs within a defined local territory in accordance with national law.
-
D.
self-governing territory
A self-governing territory is a geographically defined area that exercises autonomous control over its internal affairs under its own local government, while remaining formally subject to a larger sovereign state.
-
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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:43 p.m.