Triple
T7525180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beas–Sutlej link |
E177873
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter-basin water transfer project |
C2937
|
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: inter-basin water transfer project Context triple: [Beas–Sutlej link, instanceOf, inter-basin water transfer project]
-
A.
water transfer project
chosen
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.
-
B.
water management project
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.
-
C.
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.
-
D.
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.
-
E.
water reservoir complex
A water reservoir complex is an integrated system of interconnected reservoirs, infrastructure, and control facilities designed to store, manage, and distribute water for purposes such as supply, irrigation, flood control, and power generation.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:46 p.m.