Triple
T24942323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Sea via Lake Lothing and Mutford Lock |
E623491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | navigable waterway 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: navigable waterway route Context triple: [North Sea via Lake Lothing and Mutford Lock, instanceOf, navigable waterway route]
-
A.
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.
-
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.
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.
-
D.
waterway section
A waterway section is a defined segment of a natural or artificial watercourse, such as a river, canal, or channel, characterized by specific geographic, hydraulic, or administrative properties.
-
E.
national water trail
A national water trail is a designated waterway route recognized for its recreational, scenic, and conservation value, providing public access and facilities for activities like paddling, boating, and wildlife viewing.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:30 a.m.