Triple

T21750092
Position Surface form Disambiguated ID Type / Status
Subject North Greenwich bus station E536890 entity
Predicate hasBusRoute P39381 FINISHED
Object London Buses route 132 — NE NERFINISHED

How this triple was built (3 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: London Buses route 132 | Statement: [North Greenwich bus station, hasBusRoute, London Buses route 132]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: London Buses route 132
Context triple: [North Greenwich bus station, hasBusRoute, London Buses route 132]
  • A. London Buses route 133
    London Buses route 133 is a Transport for London bus service in south London that runs between Streatham and Liverpool Street, passing through key locations such as Brixton, Kennington, Elephant & Castle, and London Bridge.
  • B. London Buses route 134
    London Buses route 134 is a Transport for London bus service that runs between North Finchley and University College Hospital in central London, serving areas such as Muswell Hill, Highgate, and Archway.
  • C. London Buses route 112
    London Buses route 112 is a Transport for London bus service in northwest London that runs between Brent Cross and Ealing, serving several residential and commercial areas along its corridor.
  • D. London Buses route 436
    London Buses route 436 is a Transport for London bus service in south and central London that links areas such as Lewisham and Paddington via key corridors including Kennington.
  • E. London bus route 73
    London bus route 73 is a major Transport for London bus service running through central London, linking key destinations such as Oxford Street with areas including Stoke Newington and Victoria.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: London Buses route 132
Target entity description: London Buses route 132 is a Transport for London bus service in southeast London that runs between Bexleyheath and North Greenwich, serving areas such as Eltham and Kidbrooke.
  • A. London Buses route 133
    London Buses route 133 is a Transport for London bus service in south London that runs between Streatham and Liverpool Street, passing through key locations such as Brixton, Kennington, Elephant & Castle, and London Bridge.
  • B. London Buses route 134
    London Buses route 134 is a Transport for London bus service that runs between North Finchley and University College Hospital in central London, serving areas such as Muswell Hill, Highgate, and Archway.
  • C. London Buses route 112
    London Buses route 112 is a Transport for London bus service in northwest London that runs between Brent Cross and Ealing, serving several residential and commercial areas along its corridor.
  • D. London Buses route 436
    London Buses route 436 is a Transport for London bus service in south and central London that links areas such as Lewisham and Paddington via key corridors including Kennington.
  • E. London bus route 73
    London bus route 73 is a major Transport for London bus service running through central London, linking key destinations such as Oxford Street with areas including Stoke Newington and Victoria.
  • F. None of above. chosen

Provenance (2 batches)

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_69e0c46eab808190b848242d63a17c47 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a79fb74819098a247c4f31598a8 completed April 28, 2026, 2:24 a.m.
Created at: April 16, 2026, 6:50 p.m.