Triple

T34747364
Position Surface form Disambiguated ID Type / Status
Subject Northern line extension to Battersea E1001673 entity
Predicate instanceOf P0 FINISHED
Object London Underground line extension project C24427 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 line extension project
Context triple: [Northern line extension to Battersea, instanceOf, London Underground line extension project]
  • A. cross-London rail system
    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.
  • B. 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.
  • C. 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.
  • D. subway line extension chosen
    A subway line extension is an added segment of track and stations that lengthens an existing subway route to serve new areas and increase transit capacity.
  • E. 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.
  • 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_69f76db0367081909b57c50a7fb03025 completed May 3, 2026, 3:45 p.m.
Created at: May 3, 2026, 3:59 p.m.