Triple
T10134334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red River trade |
E226818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river-based transportation 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: river-based transportation network Context triple: [Red River trade, instanceOf, river-based transportation 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.
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.
-
D.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:06 p.m.