Triple

T24290049
Position Surface form Disambiguated ID Type / Status
Subject RAF Woodhall Spa E605790 entity
Predicate stationedUnit P28243 FINISHED
Object No. 619 Squadron RAF
No. 619 Squadron RAF was a Royal Air Force heavy bomber squadron that operated Avro Lancasters on strategic bombing missions during the Second World War.
E1650196 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. 619 Squadron RAF | Statement: [RAF Woodhall Spa, stationedUnit, No. 619 Squadron RAF]
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. 619 Squadron RAF
Triple: [RAF Woodhall Spa, stationedUnit, No. 619 Squadron RAF]
Generated description
No. 619 Squadron RAF was a Royal Air Force heavy bomber squadron that operated Avro Lancasters on strategic bombing missions during the Second World War.

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_69e295480d0c8190846fc3c2e2da1d4c completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f29155e3cc8190808723d6b56dcfc0 completed April 29, 2026, 11:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a101bd38d288190b185db09f18d34f4 completed May 22, 2026, 9:03 a.m.
NEDg Description generation batch_6a1023488c948190bd2b15038e087886 completed May 22, 2026, 9:35 a.m.
NED2 Entity disambiguation (via description) batch_6a10245dd05481909024cdeecaabcd20 completed May 22, 2026, 9:39 a.m.
Created at: April 18, 2026, 12:08 a.m.