Triple
T25226172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zila Parishad |
E632092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tier of Panchayati Raj |
C34719
|
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: tier of Panchayati Raj Context triple: [Zila Parishad, instanceOf, tier of Panchayati Raj]
-
A.
third-tier administrative subdivision
chosen
A third-tier administrative subdivision is a local governmental unit that operates below the second-tier division within a country's hierarchical administrative structure, typically managing community-level services and regulations.
-
B.
subdivision of a district in India
A subdivision of a district in India is an administrative unit below the district level that groups several tehsils or blocks to facilitate local governance, revenue administration, and public service delivery.
-
C.
Zilla Parishad
A Zilla Parishad is a district-level local self-government body in India responsible for planning, coordinating, and overseeing development and administrative functions across rural areas within its jurisdiction.
-
D.
township-level division
A township-level division is a local administrative unit within a country, typically governing a small urban or rural area below the county level and responsible for basic public services and local governance.
-
E.
Second-level administrative division
A second-level administrative division is a territorial unit within a country that is directly below the primary (first-level) administrative regions, such as provinces or states, and typically manages local governance and public services.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 1:03 p.m.