Triple

T2808076
Position Surface form Disambiguated ID Type / Status
Subject Dewsbury E54100 entity
Predicate hasNeighbouringSettlement P4647 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: [Dewsbury, hasNeighbouringSettlement, Ossett]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ossett
Context triple: [Dewsbury, hasNeighbouringSettlement, 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. 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.
  • E. Cornbrook
    Cornbrook is a major Metrolink tram interchange area in Manchester, England, providing key connections between multiple tram lines.
  • 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_69ab49dcee188190b5c6eca9ae9e3469 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde2fdcf88190a52e515c166ea8f7 completed March 7, 2026, 8:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69afc678d6488190be73244b7e78f30c completed March 10, 2026, 7:21 a.m.
Created at: March 6, 2026, 9:59 p.m.