Triple

T14228163
Position Surface form Disambiguated ID Type / Status
Subject Liverpool to Wigan line E352677 entity
Predicate hasStation P35 FINISHED
Object Wigan Wallgate E112387 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 Wallgate | Statement: [Liverpool to Wigan line, hasStation, Wigan Wallgate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wigan Wallgate
Context triple: [Liverpool to Wigan line, hasStation, Wigan Wallgate]
  • A. Wigan Wallgate chosen
    Wigan Wallgate is a railway station in Wigan, Greater Manchester, serving regional and commuter services on routes including those toward Manchester and Southport.
  • B. Moorgate
    Moorgate is a historic financial and commercial area in central London, known for its offices, transport links, and proximity to the heart of the City’s banking district.
  • C. Wakefield Kirkgate
    Wakefield Kirkgate is a railway station in Wakefield, West Yorkshire, England, serving as a key local and regional transport hub.
  • D. Queensgate
    Queensgate is an industrial and commercial neighborhood on the west side of downtown Cincinnati, Ohio.
  • E. Wallgate
    Wallgate is a street in the center of Wigan, England, known for giving its name to the nearby Wigan Wallgate railway station.
  • 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_69d8278adc7c8190a9218d69bce3c4e6 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de622a48508190bbfedb762bd1674d completed April 14, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd281801488190bcb17d27ee18cde6 completed May 8, 2026, 12:02 a.m.
Created at: April 10, 2026, 1:07 a.m.