Triple
T32533874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhima Irrigation Project |
E831536
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multipurpose irrigation project |
C1458
|
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: multipurpose irrigation project Context triple: [Bhima Irrigation Project, instanceOf, multipurpose irrigation project]
-
A.
multipurpose dam
A multipurpose dam is a large engineered barrier built across a river or stream to store and regulate water for multiple uses such as irrigation, hydropower generation, flood control, water supply, and recreation.
-
B.
irrigation dam
An irrigation dam is a barrier constructed across a watercourse to store and regulate water specifically for agricultural use, enabling controlled distribution to fields and crops.
-
C.
water transfer project
A water transfer project is a large-scale infrastructure system designed to move water from regions of surplus to regions of deficit through canals, pipelines, tunnels, and related facilities to meet agricultural, industrial, and domestic needs.
-
D.
irrigated district
An irrigated district is a geographically defined area where water is systematically supplied and managed, typically through infrastructure like canals and pipelines, to support agricultural production and related land uses.
-
E.
water management project
chosen
A water management project is an organized initiative that plans, develops, and operates systems and practices to sustainably collect, store, distribute, and protect water resources for human and environmental needs.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:01 a.m.