Triple
T19837810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken–Betwa River Linking Project |
E476644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river interlinking 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: river interlinking project Context triple: [Ken–Betwa River Linking Project, instanceOf, river interlinking 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.
proposed dam project
A proposed dam project is a planned infrastructure initiative to construct a barrier across a waterway for purposes such as water storage, flood control, energy generation, or irrigation, pending approval and implementation.
-
C.
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.
-
D.
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.
-
E.
levee system
A levee system is an integrated network of embankments, floodwalls, and related structures designed to contain or redirect water to protect land and infrastructure from flooding.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.