Triple

T14219564
Position Surface form Disambiguated ID Type / Status
Subject Broxbourne E352453 entity
Predicate administrativeHeadquarters P62 FINISHED
Object Cheshunt 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: Cheshunt | Statement: [Broxbourne, administrativeHeadquarters, Cheshunt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cheshunt
Context triple: [Broxbourne, administrativeHeadquarters, Cheshunt]
  • A. Cheshunt chosen
    Cheshunt is a town in Hertfordshire, England, situated just north of London and known as a commuter hub with rail links into the capital.
  • B. Hoddesdon
    Hoddesdon is a historic market town in southern England known for its traditional high street, commuter links to London, and proximity to the River Lea.
  • C. Radlett
    Radlett is a prosperous commuter village in southern England, situated between St Albans and London within the county of Hertfordshire.
  • D. Loughton
    Loughton is a suburban town in southeast England known for its proximity to Epping Forest and its role as a commuter hub within the London metropolitan area.
  • E. Epping
    Epping is a market town in the Epping Forest district of Essex, England, known for its historic high street and proximity to the ancient Epping Forest.
  • 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_69d8278a06e481908b5d6af0a8afe737 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de621258d4819085f358cd2cf109e4 completed April 14, 2026, 3:49 p.m.
Created at: April 10, 2026, 1:06 a.m.