Triple
T25218435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotterdam–Berlin–Poland inland waterway route |
E631891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inland waterway transport corridor |
C3393
|
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 corridor Context triple: [Rotterdam–Berlin–Poland inland waterway route, instanceOf, inland waterway transport corridor]
-
A.
inland waterway vessel
An inland waterway vessel is a ship or boat specifically designed and equipped for transporting goods or passengers on rivers, canals, lakes, and other sheltered inland waters.
-
B.
waterway navigation system
A waterway navigation system is an integrated set of tools, sensors, and software that provides real-time guidance, routing, and safety information for vessels traveling on rivers, canals, and other inland or coastal waterways.
-
C.
navigable waterway
chosen
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.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
E.
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.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 12:59 p.m.