Triple

T38159272
Position Surface form Disambiguated ID Type / Status
Subject S Stock E952973 entity
Predicate instanceOf P0 FINISHED
Object London Underground train C64467 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 train
Context triple: [S Stock, instanceOf, London Underground train]
  • 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 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. London Underground depot
    A London Underground depot is a specialized facility where Underground trains are stored, maintained, cleaned, and prepared for daily service on the network.
  • 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 station entrance
    A London Underground station entrance is a designated access point at street level that allows passengers to enter or exit the Tube network, typically marked by signage, stairways, escalators, or lifts leading to the station concourse and platforms.
  • 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_69f76f0b93c48190a117319ab3a9f282 completed May 3, 2026, 3:51 p.m.
Created at: May 3, 2026, 4:21 p.m.