Triple
T25701570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Coast Line and Tarka Line community rail route |
E644476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community rail partnership corridor |
C50661
|
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: community rail partnership corridor Context triple: [Atlantic Coast Line and Tarka Line community rail route, instanceOf, community rail partnership corridor]
-
A.
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.
-
B.
joint railway
A joint railway is a rail line or network that is owned, operated, or managed collaboratively by two or more railway companies or authorities, sharing infrastructure, services, and responsibilities.
-
C.
suburban railway corridor
A suburban railway corridor is a dedicated rail route connecting city centers with surrounding residential suburbs, designed to support frequent, high-capacity commuter train services.
-
D.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
-
E.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:46 p.m.