Triple

T808908
Position Surface form Disambiguated ID Type / Status
Subject Downe E17498 entity
Predicate locatedNear P294 FINISHED
Object Cudham E50599 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: Cudham | Statement: [Downe, locatedNear, Cudham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cudham
Context triple: [Downe, locatedNear, Cudham]
  • A. Cudham chosen
    Cudham is a historic rural village in southeast England, known for its traditional character and countryside setting within Greater London.
  • B. Flitcham
    Flitcham is a small rural village in Norfolk, England, known for its historic church and proximity to the royal Sandringham Estate.
  • C. Windlesham
    Windlesham is a village and civil parish in the Surrey Heath district of Surrey, England, known for its affluent residential character and leafy surroundings.
  • D. Yarnton
    Yarnton is a rural village in Oxfordshire, England, known for its historic church, manor house, and proximity to the city of Oxford.
  • E. Thatcham
    Thatcham is a historic market town in Berkshire, England, often cited as one of the oldest continuously inhabited settlements in the country.
  • 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_69a4937ae8a08190b5084a03d532b30e completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4ab256cbc8190bf75b5d5e35ff0aa completed March 1, 2026, 9:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac7f211bf88190bd6f791894ece41a completed March 7, 2026, 7:40 p.m.
Created at: March 1, 2026, 7:38 p.m.