Triple
T34694392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond and North Woolwich |
E890986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-London stopping service |
C51173
|
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-London stopping service Context triple: [Richmond and North Woolwich, instanceOf, cross-London stopping service]
-
A.
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.
-
B.
cross-London rail system
chosen
A cross-London rail system is an integrated network of rail lines and tunnels that traverse the city from one side to the other, providing high-capacity, rapid transit across central London and connecting outer suburbs.
-
C.
limited-stop bus service
A limited-stop bus service is a transit route that only stops at selected key locations rather than every stop, reducing travel time for longer-distance passengers.
-
D.
London Tramlink route
A London Tramlink route is a designated service path within the Tramlink light rail network in South London, defined by its specific sequence of stops, operating pattern, and timetable.
-
E.
London Underground line segment
A London Underground line segment is a continuous stretch of track connecting two adjacent stations on a specific Tube line, along which trains travel directly without intermediate stops.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.