Triple

T21390783
Position Surface form Disambiguated ID Type / Status
Subject Burton Road E527641 entity
Predicate servedBy P82 FINISHED
Object Burton Road tram stop NE NERFINISHED

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: Burton Road tram stop | Statement: [Burton Road, servedBy, Burton Road tram stop]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burton Road tram stop
Context triple: [Burton Road, servedBy, Burton Road tram stop]
  • A. Burton Road tram stop chosen
    Burton Road tram stop is a Metrolink light-rail station serving the West Didsbury area of Manchester, England.
  • B. Wellesley Road tram stop
    Wellesley Road tram stop is a light rail stop on the Tramlink network serving the central area of Croydon in south London.
  • C. Moor Road tram stop
    Moor Road tram stop is a light-rail station on Greater Manchester’s Metrolink network serving the Airport Line in the Wythenshawe area.
  • D. St Werburgh's Road tram stop
    St Werburgh's Road tram stop is a Manchester Metrolink light-rail station in Chorlton-cum-Hardy, serving as a key stop on the network’s Airport Line.
  • E. Dane Road tram stop
    Dane Road tram stop is a light-rail station on Greater Manchester’s Metrolink network serving the Sale area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b112a7808190ae4b180ce0d2b408 completed April 22, 2026, 11:29 a.m.
Created at: April 16, 2026, 5:13 p.m.