Triple

T22929591
Position Surface form Disambiguated ID Type / Status
Subject Shudehill Interchange E569399 entity
Predicate locatedIn P40 FINISHED
Object Shudehill 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: Shudehill | Statement: [Shudehill Interchange, locatedIn, Shudehill]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shudehill
Context triple: [Shudehill Interchange, locatedIn, Shudehill]
  • A. Shudehill chosen
    Shudehill is a central district in Manchester, England, known for its major bus and tram interchange and proximity to the city’s main shopping and commercial areas.
  • B. Etchinghill
    Etchinghill is a small village in Kent, England, situated near Folkestone and known for its rural setting and proximity to the North Downs.
  • C. Credenhill
    Credenhill is a village in Herefordshire, England, known for its rural setting and proximity to military facilities such as Stirling Lines.
  • D. Birkhill
    Birkhill is a village in the Angus council area of Scotland, known as a residential community near the city of Dundee.
  • E. Birkhill
    Birkhill is a heritage railway station on the preserved Bo’ness and Kinneil Railway in Scotland, serving as a stop for tourist and enthusiast train services.
  • 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_69e2458f7d008190901dccbaebeaba24 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f180dc33e8819099e5ad87207de57f completed April 29, 2026, 3:54 a.m.
Created at: April 17, 2026, 3:44 p.m.