Triple

T33811372
Position Surface form Disambiguated ID Type / Status
Subject RAF Swinderby E866544 entity
Predicate locatedNear P294 FINISHED
Object Swinderby, Lincolnshire
Swinderby, Lincolnshire is a small village in the East Midlands of England, historically associated with the nearby former Royal Air Force station RAF Swinderby.
E2069022 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: Swinderby, Lincolnshire | Statement: [RAF Swinderby, locatedNear, Swinderby, Lincolnshire]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Swinderby, Lincolnshire
Triple: [RAF Swinderby, locatedNear, Swinderby, Lincolnshire]
Generated description
Swinderby, Lincolnshire is a small village in the East Midlands of England, historically associated with the nearby former Royal Air Force station RAF Swinderby.

Provenance (5 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_69f349911a8c81908478662194b23d8c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6ffcddfc08190bb83e4f2de5bee7b completed May 3, 2026, 7:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a366e96b50881908b80071978a5976d completed June 20, 2026, 10:42 a.m.
NEDg Description generation batch_6a366f5729ac81908599bc91632a5242 completed June 20, 2026, 10:45 a.m.
NED2 Entity disambiguation (via description) batch_6a366fddebcc81909aba7e3fcadb83bc completed June 20, 2026, 10:47 a.m.
Created at: May 1, 2026, 1:46 a.m.