Triple

T12762311
Position Surface form Disambiguated ID Type / Status
Subject National Express E305024 entity
Predicate operatesOnRoute P70721 FINISHED
Object London–Birmingham E23213 NE FINISHED

How this triple was built (2 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–Birmingham | Statement: [National Express, operatesOnRoute, London–Birmingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: London–Birmingham
Context triple: [National Express, operatesOnRoute, London–Birmingham]
  • A. Birmingham – Manchester
    Birmingham–Manchester is a key intercity rail route in England linking the West Midlands city of Birmingham with the northern city of Manchester via intermediate stations such as Stafford.
  • B. London–Leeds
    London–Leeds is a major intercity rail corridor in the United Kingdom linking the capital with the key northern city of Leeds.
  • C. London Euston – Birmingham chosen
    London Euston – Birmingham is a major intercity rail corridor in England linking the capital with the West Midlands.
  • D. London–York
    London–York is a major intercity rail corridor in England linking the capital with the historic city of York.
  • E. London to Liverpool
    London to Liverpool is a major intercity rail corridor in England linking the capital with the key northwestern city of Liverpool.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d8f9f588190bffdea878856204b completed April 10, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69f684f298f881908ad77f2d0ab588a8 completed May 2, 2026, 11:12 p.m.
Created at: April 9, 2026, 5:28 p.m.