Triple

T21230744
Position Surface form Disambiguated ID Type / Status
Subject Hoddesdon E523205 entity
Predicate hasPostTown P2711 FINISHED
Object Hoddesdon 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: Hoddesdon | Statement: [Hoddesdon, hasPostTown, Hoddesdon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoddesdon
Context triple: [Hoddesdon, hasPostTown, Hoddesdon]
  • A. Hoddesdon chosen
    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.
  • B. Radlett
    Radlett is a prosperous commuter village in southern England, situated between St Albans and London within the county of Hertfordshire.
  • C. Welwyn
    Welwyn is a historic village and civil parish in Hertfordshire, England, known for its Roman heritage and picturesque rural character.
  • D. Welwyn Hatfield
    Welwyn Hatfield is a local government district and borough in Hertfordshire, England, that includes the towns of Welwyn Garden City and Hatfield.
  • E. Kelvedon
    Kelvedon is a village and civil parish in Essex, England, known for its historic High Street and role as a commuter settlement with rail links to London.
  • 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734af3d508190b3359d14496370b6 completed April 21, 2026, 8:26 a.m.
Created at: April 16, 2026, 3:45 p.m.