Triple
T34548503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Waterloo to Weymouth |
E886998
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Western Main Line service |
C20256
|
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: South Western Main Line service Context triple: [London Waterloo to Weymouth, instanceOf, South Western Main Line service]
-
A.
Yarra Trams service
A Yarra Trams service is an individual scheduled tram journey operated on Melbourne’s tram network, defined by its route, timetable, and vehicle providing passenger transport between designated stops.
-
B.
London Underground service pattern
A London Underground service pattern is the structured arrangement of train routes, frequencies, stopping points, and operating times across the network that determines how services run on each line and branch.
-
C.
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.
-
D.
Sheffield Supertram route
A Sheffield Supertram route is a defined public transport service path within the Sheffield light rail network, specifying the sequence of stops, track segments, and operational patterns followed by trams between termini.
-
E.
railway line service pattern
chosen
A railway line service pattern defines the structured arrangement of train services over a route, including stopping sequences, frequencies, and service types that determine how trains operate along the line.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.