Triple
T18914716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee River navigation system |
E462695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | waterway infrastructure network |
C6053
|
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: waterway infrastructure network Context triple: [Tennessee River navigation system, instanceOf, waterway infrastructure network]
-
A.
waterway network
chosen
A waterway network is an interconnected system of natural and artificial water channels (such as rivers, canals, and streams) designed or utilized for the movement, distribution, and management of water and waterborne transport.
-
B.
canal infrastructure
Canal infrastructure encompasses the engineered systems, structures, and facilities—such as channels, locks, dams, embankments, and control mechanisms—designed to manage and support waterborne transport, irrigation, drainage, and water regulation along artificial waterways.
-
C.
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.
-
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.
engineered waterway
An engineered waterway is a human-made or heavily modified channel or system designed to control, convey, or manage water for purposes such as navigation, irrigation, drainage, flood control, or 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:58 a.m.