Triple

T12495237
Position Surface form Disambiguated ID Type / Status
Subject City of Wakefield E298666 entity
Predicate contains P35 FINISHED
Object Ossett E149687 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: Ossett | Statement: [City of Wakefield, contains, Ossett]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ossett
Context triple: [City of Wakefield, contains, Ossett]
  • A. Ossett chosen
    Ossett is a market town in northern England that forms part of the City of Wakefield metropolitan borough in West Yorkshire.
  • B. Glossop
    Glossop is a market town in Derbyshire, England, situated on the edge of the Peak District and historically associated with the textile industry.
  • C. Helsby
    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.
  • D. Wellesbourne
    Wellesbourne is a large English village in Warwickshire, known for its historic airfield and proximity to Stratford-upon-Avon.
  • E. Banbury
    Banbury is a historic market town in Oxfordshire, England, known for its medieval cross, canal-side setting, and association with the traditional Banbury cake.
  • 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_69d6ada4cd388190ae3bbf83ff87057a completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94de4089c8190917a45365e641437 completed April 10, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64badad488190ae1c6c2883a88a4b completed May 2, 2026, 7:08 p.m.
Created at: April 8, 2026, 9:57 p.m.