Triple

T18608507
Position Surface form Disambiguated ID Type / Status
Subject Cannock Chase District E454822 entity
Predicate contains P35 FINISHED
Object Hednesford 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: Hednesford | Statement: [Cannock Chase District, contains, Hednesford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hednesford
Context triple: [Cannock Chase District, contains, Hednesford]
  • A. Hednesford chosen
    Hednesford is a small town in Staffordshire, England, situated near Cannock Chase and known historically for its coal mining heritage.
  • B. Ombersley
    Ombersley is a village and civil parish in Worcestershire, England, known for its historic timber-framed buildings and rural riverside setting.
  • C. Pershore
    Pershore is a historic market town on the River Avon in Worcestershire, England, known for its Georgian architecture and annual plum festival.
  • D. Droitwich
    Droitwich is a historic spa town in Worcestershire, England, long known for its salt springs and brine baths.
  • E. Eccleshall
    Eccleshall is a historic market town and civil parish in Staffordshire, England, known for its traditional architecture and rural surroundings.
  • 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_69d8d38bbe7c8190bdec3138e7d413c9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54cff3be8819080ab20045bd18a4d completed April 19, 2026, 9:45 p.m.
Created at: April 10, 2026, 11:45 a.m.