Triple
T24356524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Mary River (via diversion) |
E613937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | water diversion |
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 Context triple: [St. Mary River (via diversion), instanceOf, water diversion]
-
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.
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.
-
C.
water supply dam
A water supply dam is a barrier constructed across a watercourse to store and regulate water primarily for human consumption, irrigation, and other municipal or industrial uses.
-
D.
water infrastructure
Water infrastructure encompasses the systems, facilities, and networks designed to source, treat, store, distribute, and manage water and wastewater for human, industrial, and environmental needs.
-
E.
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.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2 a.m.