Triple

T14726461
Position Surface form Disambiguated ID Type / Status
Subject Lechlade E345956 entity
Predicate locatedNear P294 FINISHED
Object Fairford E174038 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: Fairford | Statement: [Lechlade, locatedNear, Fairford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fairford
Context triple: [Lechlade, locatedNear, Fairford]
  • A. Fairford chosen
    Fairford is a small market town in Gloucestershire, England, known for its historic wool church and proximity to RAF Fairford airbase.
  • B. Highworth
    Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
  • C. Wyndford
    Wyndford is a residential neighborhood in the Maryhill area of Glasgow, Scotland, known for its post-war housing estates and close-knit community.
  • D. Belchford
    Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
  • E. Yarrowford
    Yarrowford is a small village in the Scottish Borders region of Scotland, situated in the Yarrow Valley near the River Yarrow.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec26013c8819090512f8b4df9cc87 completed April 14, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdf099eaf48190b89032b6ac769e67 completed May 8, 2026, 2:18 p.m.
Created at: April 10, 2026, 1:29 a.m.