Triple

T14090223
Position Surface form Disambiguated ID Type / Status
Subject River Stort E339107 entity
Predicate confluenceNear P8203 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: [River Stort, confluenceNear, Hoddesdon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoddesdon
Context triple: [River Stort, confluenceNear, 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. Cheshunt
    Cheshunt is a town in Hertfordshire, England, situated just north of London and known as a commuter hub with rail links into the capital.
  • 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_69d81c687b0c819087fd9ed4198403f8 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5ee3213c8190af2853a2a5b302a2 completed April 14, 2026, 3:36 p.m.
Created at: April 9, 2026, 10:21 p.m.