Triple
T8683883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unified Deep Water System of European Russia |
E206104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inland water transport system |
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 water transport system Context triple: [Unified Deep Water System of European Russia, instanceOf, inland water transport system]
-
A.
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.
-
B.
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.
-
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.
canal infrastructure
Canal infrastructure encompasses the engineered systems, structures, and facilities—such as channels, locks, dams, embankments, and control mechanisms—designed to manage and support waterborne transport, irrigation, drainage, and water regulation along artificial waterways.
-
E.
levee system
A levee system is an integrated network of embankments, floodwalls, and related structures designed to contain or redirect water to protect land and infrastructure from flooding.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.