Triple

T18362860
Position Surface form Disambiguated ID Type / Status
Subject Taston E439962 entity
Predicate near P350 FINISHED
Object Spelsbury 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: Spelsbury | Statement: [Taston, near, Spelsbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spelsbury
Context triple: [Taston, near, Spelsbury]
  • A. Spelsbury chosen
    Spelsbury is a small rural village in Oxfordshire, England, known for its historic church and traditional Cotswold character.
  • B. Wraysbury
    Wraysbury is a village and civil parish in Berkshire, England, situated near the River Thames and known for its historic sites and proximity to Windsor.
  • C. Baltonsborough
    Baltonsborough is a rural village in Somerset, England, known for its agricultural landscape and proximity to the historic town of Glastonbury.
  • D. Youlbury
    Youlbury is a rural locality in Oxfordshire, England, known historically as the place where archaeologist Sir Arthur Evans died.
  • E. Woodnesborough
    Woodnesborough is a small village and civil parish in Kent, England, known for its rural character and historic church.
  • 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_69d8b918221c8190a9f7b563d64ac677 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e516dd973c8190857c588ab9ad9daf completed April 19, 2026, 5:54 p.m.
Created at: April 10, 2026, 10:37 a.m.