Triple
T32744735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uluberia II community development block |
E837323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rural administrative unit |
C42637
|
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 administrative unit Context triple: [Uluberia II community development block, instanceOf, rural administrative unit]
-
A.
rural administrative district
chosen
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.
commune-level administrative unit
A commune-level administrative unit is the smallest local government division within a country, typically responsible for basic public services, local regulations, and community administration for a town, village, or small group of settlements.
-
C.
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.
-
D.
rural province
A rural province is a largely non-urban administrative region characterized by low population density, agricultural or natural-resource-based economies, and small, dispersed communities.
-
E.
rural community region
A rural community region is a geographically defined area characterized by low population density, predominantly agricultural or natural land use, and closely interconnected local communities with shared services, culture, and infrastructure.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:12 a.m.