Triple

T27180326
Position Surface form Disambiguated ID Type / Status
Subject RAF Linton-on-Ouse E683172 entity
Predicate hostedUnit P3556 FINISHED
Object No. 426 Squadron RCAF
No. 426 Squadron RCAF was a Royal Canadian Air Force bomber squadron that served in Europe during the Second World War as part of RAF Bomber Command.
E1764163 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: No. 426 Squadron RCAF | Statement: [RAF Linton-on-Ouse, hostedUnit, No. 426 Squadron RCAF]
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: No. 426 Squadron RCAF
Triple: [RAF Linton-on-Ouse, hostedUnit, No. 426 Squadron RCAF]
Generated description
No. 426 Squadron RCAF was a Royal Canadian Air Force bomber squadron that served in Europe during the Second World War as part of RAF Bomber Command.

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_69eefad086808190ab89816c0c300476 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f6257cec68819089da3874cf1ac740 completed May 2, 2026, 4:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1262648bb881908af64157017170cb completed May 24, 2026, 2:28 a.m.
NEDg Description generation batch_6a12686ad9cc8190a4c36c60d8d99104 completed May 24, 2026, 2:54 a.m.
NED2 Entity disambiguation (via description) batch_6a126901467481909e689c279e3516c1 completed May 24, 2026, 2:57 a.m.
Created at: April 27, 2026, 9:28 a.m.