Triple

T12606907
Position Surface form Disambiguated ID Type / Status
Subject Batley railway station E301002 entity
Predicate connectsBatleyTo P11435 FINISHED
Object Wigan E34961 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: Wigan | Statement: [Batley railway station, connectsBatleyTo, Wigan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wigan
Context triple: [Batley railway station, connectsBatleyTo, Wigan]
  • A. Wigan chosen
    Wigan is a large town in North West England known historically for its coal mining and cotton industries and today for its rugby league and football clubs.
  • B. Salford
    Salford is a city in Greater Manchester, England, known for its industrial heritage and the modern MediaCityUK development on the Salford Quays.
  • C. Salford
    Salford is a small rural village in the West Oxfordshire district of Oxfordshire, England.
  • D. Oldham
    Oldham is an English-origin surname borne by various notable individuals across literature, politics, and other fields.
  • E. Rochdale
    Rochdale is a large town in Greater Manchester, England, historically known as a mill town and cooperative movement birthplace, now serving as a residential and commercial hub connected by rail to Manchester.
  • 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_69d7bdea2ca881908f379526c13b1145 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d960c2e5b88190a7cc16002b218d8a completed April 10, 2026, 8:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6686395c081909410b429fce6ebf8 completed May 2, 2026, 9:10 p.m.
Created at: April 9, 2026, 5:11 p.m.