Triple

T11495749
Position Surface form Disambiguated ID Type / Status
Subject BD postcode area E272529 entity
Predicate coversTown P847 FINISHED
Object Cleckheaton E303339 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: Cleckheaton | Statement: [BD postcode area, coversTown, Cleckheaton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cleckheaton
Context triple: [BD postcode area, coversTown, Cleckheaton]
  • A. Cleckheaton chosen
    Cleckheaton is a town in West Yorkshire, England, historically part of the Heavy Woollen District and known for its textile industry heritage.
  • B. Knottingley
    Knottingley is a small town in West Yorkshire, England, historically known for its glassmaking and situated on the banks of the River Aire.
  • C. Beckum
    Beckum is a town in the district of Warendorf in North Rhine-Westphalia, Germany, known historically for its cement industry and location in the Münsterland region.
  • D. Mirfield
    Mirfield is a small town in West Yorkshire, England, known for its position on major rail routes and its historic textile industry.
  • E. Acomb
    Acomb is a village in Northumberland, England, situated near Hexham and known for its rural character and historic surroundings.
  • 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85de183f08190abfa36eaabc61dc6 completed April 10, 2026, 2:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69ee86853e088190a9c1378aad45fa18 completed April 26, 2026, 9:41 p.m.
Created at: April 8, 2026, 9:36 p.m.