Triple
T15666436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellingham–Alaska route |
E377198
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-distance ferry corridor |
C2952
|
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: long-distance ferry corridor Context triple: [Bellingham–Alaska route, instanceOf, long-distance ferry corridor]
-
A.
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.
-
B.
transport corridor
chosen
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.
-
C.
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.
-
D.
passenger ferry
A passenger ferry is a vessel designed to transport people, and sometimes light vehicles or cargo, across bodies of water on regular, short-distance routes.
-
E.
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.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:16 a.m.