Triple

T10509366
Position Surface form Disambiguated ID Type / Status
Subject Wormley E247870 entity
Predicate locatedNorthOf P305 FINISHED
Object Cheshunt E310201 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: Cheshunt | Statement: [Wormley, locatedNorthOf, Cheshunt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cheshunt
Context triple: [Wormley, locatedNorthOf, 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 suburb in Melbourne, Australia, known for its residential communities, shopping facilities, and role as a transport hub in the city's northern corridor.
  • 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_69d381c4aa948190942e1d803143fb0e completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d509b359ac8190b3683cc6b9c70a71 completed April 7, 2026, 1:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69f470cbce14819099d47d468ae61df7 completed May 1, 2026, 9:22 a.m.
Created at: April 6, 2026, 12:27 p.m.