Triple

T2777472
Position Surface form Disambiguated ID Type / Status
Subject Windsor and Maidenhead E61607 entity
Predicate contains P35 FINISHED
Object Datchet E281996 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: Datchet | Statement: [Windsor and Maidenhead, contains, Datchet]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Datchet
Context triple: [Windsor and Maidenhead, contains, Datchet]
  • A. Datchet chosen
    Datchet is a riverside village and civil parish in Berkshire, England, situated on the River Thames near Windsor.
  • 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. Chesham
    Chesham is a market town in the Chiltern Hills of Buckinghamshire, England, known historically for its boot, brush, and woodenware industries.
  • D. Potters Bar
    Potters Bar is a commuter town in southern England, located just north of London and known for its residential character and transport links.
  • E. Norbiton
    Norbiton is a suburban area in southwest London, England, situated within the Royal Borough of Kingston upon Thames.
  • 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_69ab4b7e43c48190997b8fc8fb1663ab completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdd82a864819082bd1181a16d5208 completed March 7, 2026, 8:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69be43705d708190abea669829ef2970 completed March 21, 2026, 7:06 a.m.
Created at: March 6, 2026, 9:57 p.m.