Triple

T3193909
Position Surface form Disambiguated ID Type / Status
Subject Upavon E66889 entity
Predicate civilParish P2739 FINISHED
Object Upavon E66889 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: Upavon | Statement: [Upavon, civilParish, Upavon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Upavon
Context triple: [Upavon, civilParish, Upavon]
  • A. Upavon chosen
    Upavon is a village on Salisbury Plain in Wiltshire, England, notable for its long military association and nearby army and air force facilities.
  • B. Wicken
    Wicken is a small rural village in East Cambridgeshire, England, best known for its proximity to the National Trust’s Wicken Fen nature reserve, one of the country’s oldest wetlands.
  • C. Yattendon
    Yattendon is a small village and civil parish in Berkshire, England, known for its rural character and historic buildings.
  • D. Blyford
    Blyford is a small rural village located in the English county of Suffolk.
  • E. Swinbrook
    Swinbrook is a small, picturesque village in rural Oxfordshire, England, known for its traditional stone cottages and historic church.
  • 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_69ad8588ba18819086a10951c32ecb80 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada714dbcc8190a7ad21b3c957f151 completed March 8, 2026, 4:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69b262181a4c8190b31bbb6bd7bef436 completed March 12, 2026, 6:50 a.m.
Created at: March 8, 2026, 3:07 p.m.