Triple
T16352542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurotunnel Shuttle terminals |
E397094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-Channel transport infrastructure |
C37322
|
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: cross-Channel transport infrastructure Context triple: [Eurotunnel Shuttle terminals, instanceOf, cross-Channel transport infrastructure]
-
A.
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.
-
B.
combined road and rail bridge–tunnel
A combined road and rail bridge–tunnel is a hybrid transportation structure that integrates both bridge and tunnel segments to carry vehicular and rail traffic across or under a geographic obstacle such as a body of water or valley.
-
C.
bridge–tunnel complex
A bridge–tunnel complex is an integrated transportation structure that combines bridge spans and underwater tunnels to carry traffic across wide bodies of water or other large obstacles.
-
D.
transport infrastructure agreement
A transport infrastructure agreement is a formal contract between parties that defines the responsibilities, funding, timelines, and performance standards for planning, building, operating, or maintaining transportation facilities such as roads, railways, ports, or airports.
-
E.
road and rail bridge
A road and rail bridge is a structure that spans physical obstacles to simultaneously carry both vehicular road traffic and railway lines across them.
- F. None of above. chosen
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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.