Triple

T21116587
Position Surface form Disambiguated ID Type / Status
Subject Helsby Football Club E520314 entity
Predicate locatedIn P40 FINISHED
Object Helsby 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: Helsby | Statement: [Helsby Football Club, locatedIn, Helsby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Helsby
Context triple: [Helsby Football Club, locatedIn, Helsby]
  • A. Helsby chosen
    Helsby is a village and civil parish in Cheshire, England, known for its railway station on the Manchester–Chester line and its prominent sandstone hill, Helsby Hill.
  • B. Ellesborough
    Ellesborough is a small village and civil parish in Buckinghamshire, England, situated in the Chiltern Hills near the Prime Minister’s country residence at Chequers.
  • C. Wellesbourne
    Wellesbourne is a large English village in Warwickshire, known for its historic airfield and proximity to Stratford-upon-Avon.
  • D. Blisworth
    Blisworth is a village in Northamptonshire, England, known for its historic location on the Grand Union Canal near the Blisworth Tunnel.
  • E. Knaphill
    Knaphill is a suburban village in Surrey, England, forming part of the borough of Woking.
  • 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_69e0b509a318819092fbbcb21d1fe603 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72106a3b48190a0efa51a74ae21f0 completed April 21, 2026, 7:02 a.m.
Created at: April 16, 2026, 2:55 p.m.