Triple
T24010860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhule Zilla Parishad |
E594526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rural local self-government body |
C15097
|
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: rural local self-government body Context triple: [Dhule Zilla Parishad, instanceOf, rural local self-government body]
-
A.
rural administrative district
A rural administrative district is a defined geographic area outside urban centers that is governed as a single unit for local administration, services, and regulation of predominantly agricultural or sparsely populated communities.
-
B.
rural organization
A rural organization is a structured group or entity that operates within and serves the needs of rural communities, focusing on local development, resource management, and community well-being.
-
C.
local governmental entity
chosen
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
D.
organ of the rural district
An organ of the rural district is an official body or authority within a rural administrative area responsible for executing local governance functions, implementing policies, and managing public services for the district’s inhabitants.
-
E.
rural commune
A rural commune is a small, self-governing community in a countryside area, typically organized around shared resources, local agriculture, and collective decision-making.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:41 p.m.