Triple
T12903706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia River at Grand Coulee Dam |
E308676
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulated river reach |
C32060
|
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 reach Context triple: [Columbia River at Grand Coulee Dam, instanceOf, regulated river reach]
-
A.
navigable waterway
A navigable waterway is a natural or artificial body of water, such as a river, canal, or channel, that is deep and wide enough for vessels to travel safely for transportation or commerce.
-
B.
river basin district
A river basin district is a designated geographical area comprising one or more neighboring river basins, including their associated groundwater and coastal waters, managed as a single unit for integrated water resources planning and protection.
-
C.
river basin
A river basin is the land area drained by a river and all its tributaries, bounded by topographic divides that separate it from adjacent basins.
-
D.
river corridor
A river corridor is the linear landscape surrounding a river, including its channel, banks, floodplain, and adjacent habitats, through which water, sediment, organisms, and energy flow and interact.
-
E.
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.
- F. None of above. chosen
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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:40 p.m.