Triple
T16874889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stranraer–Larne ferry (historical alignment) |
E421273
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former transport corridor segment |
C15590
|
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: former transport corridor segment Context triple: [Stranraer–Larne ferry (historical alignment), instanceOf, former transport corridor segment]
-
A.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
B.
freight rail corridor
A freight rail corridor is a designated railway route primarily used for the efficient, high-capacity movement of goods and cargo between industrial, commercial, and logistics hubs.
-
C.
former transit line
chosen
A former transit line is a previously operational public transportation route, such as a bus, tram, or rail line, that has been permanently discontinued or replaced.
-
D.
planned transit corridor
A planned transit corridor is a designated route or area reserved for future development of public transportation infrastructure, such as bus rapid transit or rail lines, to guide growth and improve regional mobility.
-
E.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:29 a.m.