Triple
T10550100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schoharie–Esopus water diversion system |
E248924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | water diversion system |
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: water diversion system Context triple: [Schoharie–Esopus water diversion system, instanceOf, water diversion system]
-
A.
diversion dam
A diversion dam is a low barrier built across a river or stream to redirect water into canals, pipelines, or other conveyance systems for irrigation, municipal use, or hydropower, rather than for large-scale storage.
-
B.
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.
-
C.
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.
-
D.
water supply system
A water supply system is an interconnected network of sources, treatment facilities, storage structures, and distribution pipelines designed to deliver safe and reliable water to end users.
-
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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:34 p.m.