Triple

T18658454
Position Surface form Disambiguated ID Type / Status
Subject Lower Heyford E456127 entity
Predicate locatedNear P294 FINISHED
Object Upper Heyford 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: Upper Heyford | Statement: [Lower Heyford, locatedNear, Upper Heyford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Upper Heyford
Context triple: [Lower Heyford, locatedNear, Upper Heyford]
  • A. Upper Heyford chosen
    Upper Heyford is a village in Oxfordshire, England, historically notable for its nearby former RAF airbase and its rural setting along the River Cherwell.
  • B. Lower Heyford
    Lower Heyford is a small rural village and civil parish in Oxfordshire, England, known for its historic canal, railway connections, and traditional stone-built houses.
  • C. Martlesham Heath
    Martlesham Heath is a village and residential area in Suffolk, England, known for its planned development and historical links to aviation and telecommunications research.
  • D. Lyneham
    Lyneham is a small rural village located within the district of West Oxfordshire in Oxfordshire, England.
  • E. Lyneham
    Lyneham is a residential suburb in Canberra, Australia, known for its tree-lined streets, sporting facilities, and proximity to the city centre.
  • 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_69d8d38ea1e88190997e9b231190ba6f completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e55087ae8081909cb4c0ce6c809d55 completed April 19, 2026, 10 p.m.
Created at: April 10, 2026, 11:48 a.m.