Triple

T27380916
Position Surface form Disambiguated ID Type / Status
Subject Handley Page Heyford E691223 entity
Predicate usedByUnit P22634 FINISHED
Object No. 166 Squadron RAF
No. 166 Squadron RAF was a Royal Air Force bomber unit that served primarily during the Second World War, flying heavy bombers in strategic bombing operations over Europe.
E2128461 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. 166 Squadron RAF | Statement: [Handley Page Heyford, usedByUnit, No. 166 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. 166 Squadron RAF
Triple: [Handley Page Heyford, usedByUnit, No. 166 Squadron RAF]
Generated description
No. 166 Squadron RAF was a Royal Air Force bomber unit that served primarily during the Second World War, flying heavy bombers in strategic bombing operations over Europe.

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_69ef52022538819081f873d0c84a6dd6 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62c8660108190a95c0600752d0758 completed May 2, 2026, 4:55 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37faf10df88190851cc01ceb32bf51 completed June 21, 2026, 2:53 p.m.
NEDg Description generation batch_6a37fb60247881909a9c8f5b3abafcc7 completed June 21, 2026, 2:55 p.m.
NED2 Entity disambiguation (via description) batch_6a37fbc5b384819082e85c6d9de3d3fc completed June 21, 2026, 2:57 p.m.
Created at: April 27, 2026, 12:22 p.m.