Triple
T4347706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inland Waterway System of the United States |
E97945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inland waterway 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: inland waterway network Context triple: [Inland Waterway System of the United States, instanceOf, inland waterway 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.
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.
-
C.
inland port
An inland port is a logistics and transportation hub located away from coastal seaports, typically along rivers, canals, or rail corridors, that facilitates the transfer, storage, and distribution of goods between different modes of transport.
-
D.
river
A river is a natural flowing body of water, usually freshwater, that moves continuously along a defined channel from higher elevations toward lower ones, often emptying into a sea, lake, or another river.
-
E.
river basin organization
A river basin organization is an institutional body responsible for coordinating the management, development, and protection of water and related resources within a defined river basin across sectors and jurisdictions.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:15 p.m.