Triple

T9974728
Position Surface form Disambiguated ID Type / Status
Subject Bury Market E196297 entity
Predicate near P350 FINISHED
Object Bury Interchange E196300 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: Bury Interchange | Statement: [Bury Market, near, Bury Interchange]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bury Interchange
Context triple: [Bury Market, near, Bury Interchange]
  • A. Bury Interchange chosen
    Bury Interchange is a major public transport hub in Bury, Greater Manchester, combining bus and Metrolink tram services for the town and surrounding area.
  • B. Shudehill Interchange
    Shudehill Interchange is a major public transport hub in Manchester, England, integrating bus and tram services near the city centre.
  • C. Meadowhall Interchange
    Meadowhall Interchange is a major public transport hub in Sheffield, England, linking rail, tram, and bus services for access to the Meadowhall Shopping Centre and the wider region.
  • D. Bradford Interchange
    Bradford Interchange is a major combined rail and bus station serving the city of Bradford in West Yorkshire, England.
  • E. Eccles Interchange
    Eccles Interchange is a public transport hub in Eccles, Greater Manchester, providing integrated bus, rail, and tram services for the surrounding area.
  • 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_69ca82eea2b88190a0e511d21a31f386 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb849da448190b826cb8fbf2eeb89 completed April 2, 2026, 12:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69d23ddcc01c8190bb00ac13cbbbb1fb completed April 5, 2026, 10:47 a.m.
Created at: March 30, 2026, 8:48 p.m.