Triple
T25543230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epping to Ongar branch |
E640226
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former London Underground line |
C48184
|
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: former London Underground line Context triple: [Epping to Ongar branch, instanceOf, former London Underground line]
-
A.
London Underground precursor
A London Underground precursor is any early urban rail or transport system, proposal, or technological development that directly influenced or led to the creation of the London Underground.
-
B.
disused London Underground railway branch
chosen
A disused London Underground railway branch is a former section of the Tube network, once used for passenger or freight services, that has been permanently closed and left out of regular operation.
-
C.
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.
-
D.
former transit line
A former transit line is a previously operational public transportation route, such as a bus, tram, or rail line, that has been permanently discontinued or replaced.
-
E.
former London, Brighton and South Coast Railway network
The former London, Brighton and South Coast Railway network comprises the historic system of main lines, branch lines, and associated infrastructure once operated by the LB&SCR in southern England, primarily serving routes between London, the Sussex coast, and surrounding areas before railway grouping.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:27 p.m.