Triple
T32467938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swift River (controlled releases) |
E829764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulated river flow |
C50487
|
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: regulated river flow Context triple: [Swift River (controlled releases), instanceOf, regulated river flow]
-
A.
regulated river reach
A regulated river reach is a segment of a river whose flow, water level, or timing is intentionally controlled by human-made structures such as dams, weirs, or diversion works.
-
B.
re-regulating dam
chosen
A re-regulating dam is a secondary dam built downstream of a main dam to smooth out fluctuating releases, stabilizing river flow and improving conditions for water use and ecosystems.
-
C.
river conservancy
River conservancy is the management and protection of river ecosystems through planning, regulation, restoration, and sustainable use to maintain their ecological health and benefits to society.
-
D.
riverine force
A riverine force is a military or security unit specialized in conducting operations, patrols, and logistical support on rivers and inland waterways using small boats and related craft.
-
E.
flood control facility
A flood control facility is an engineered structure or system designed to manage, divert, store, or reduce excess water flow to prevent or mitigate flooding in surrounding areas.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:57 a.m.