Triple
T30161389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle line inner London orbital services |
E766675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | London Underground service pattern |
C56223
|
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: London Underground service pattern Context triple: [Circle line inner London orbital services, instanceOf, London Underground service pattern]
-
A.
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.
-
B.
London Underground interchange
A London Underground interchange is a station or complex where passengers can transfer between two or more Underground lines (and sometimes other rail services) within a single integrated facility.
-
C.
metro network
A metro network is an interconnected system of urban rail lines, stations, and supporting infrastructure designed to transport large numbers of passengers efficiently within and around a city.
-
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 abbreviation
A London Underground line abbreviation is a short alphanumeric code or shortened name used to uniquely identify and reference a specific tube line within the London Underground network.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:21 p.m.