Triple
T3869335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European inland shipping network |
E91944
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inland waterway transport 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 transport network Context triple: [European inland shipping network, instanceOf, inland waterway transport 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.
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.
-
D.
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.
-
E.
Panama Canal infrastructure
Panama Canal infrastructure encompasses the system of locks, channels, dams, ports, support facilities, and control technologies that enable the transit, management, and maintenance of maritime traffic through the Panama Canal.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.