Triple
T35447416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urban Local Bodies system of Uttar Pradesh |
E1024524
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local self-government framework |
C8884
|
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-government framework Context triple: [Urban Local Bodies system of Uttar Pradesh, instanceOf, local self-government framework]
-
A.
system of local government
chosen
A system of local government is an organized framework of institutions, powers, and processes through which local authorities manage public services, enforce regulations, and represent community interests within a defined geographic area.
-
B.
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.
-
C.
municipal policy framework
A municipal policy framework is a structured set of principles, regulations, and procedures that guide a city or local government's decision-making, service delivery, and long-term planning.
-
D.
municipal-style government
A municipal-style government is a localized governing body responsible for managing public services, regulations, and community affairs within a city or town jurisdiction.
-
E.
sub‑national government
A sub-national government is a governing authority below the national level—such as a state, province, region, or municipality—that exercises political, administrative, and often fiscal powers within a defined territorial jurisdiction.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.