Triple
T33600935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dnieper–Black Sea waterway |
E860718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inland water transport route |
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 water transport route Context triple: [Dnieper–Black Sea waterway, instanceOf, inland water transport route]
-
A.
riverine trade route
A riverine trade route is a navigable waterway along a river system used for the transport and exchange of goods, people, and cultural influences between settlements.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
waterway network
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.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.