Triple
T31744796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hull–Rotterdam |
E810239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | North Sea ferry connection |
C48167
|
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: North Sea ferry connection Context triple: [Hull–Rotterdam, instanceOf, North Sea ferry connection]
-
A.
ferry crossing
chosen
A ferry crossing is a designated route or location where a ferry transports passengers, vehicles, or goods across a body of water between two points.
-
B.
cross-Channel transport infrastructure
Cross-Channel transport infrastructure encompasses the physical and operational systems—such as tunnels, ports, terminals, and associated logistics facilities—that enable the movement of people and goods between the UK and mainland Europe across the English Channel.
-
C.
ferry service network
A ferry service network is a coordinated system of water-based transport routes, vessels, terminals, and schedules that moves passengers and cargo between multiple ports or coastal locations.
-
D.
ferry service
A ferry service is a transportation operation that regularly carries passengers, vehicles, and sometimes cargo across bodies of water along fixed routes and schedules.
-
E.
cross-sea bridge
A cross-sea bridge is a large-scale transportation structure that spans a body of sea water to connect two land areas, enabling the passage of vehicles, trains, or pedestrians across marine environments.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:26 p.m.