Triple

T27266213
Position Surface form Disambiguated ID Type / Status
Subject RAF Ford E687910 entity
Predicate hostedUnit P3556 FINISHED
Object No. 602 Squadron RAF
No. 602 Squadron RAF is a Royal Auxiliary Air Force squadron best known for its fighter operations during the Second World War, including its role in the Battle of Britain.
E2048676 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. 602 Squadron RAF | Statement: [RAF Ford, hostedUnit, No. 602 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. 602 Squadron RAF
Triple: [RAF Ford, hostedUnit, No. 602 Squadron RAF]
Generated description
No. 602 Squadron RAF is a Royal Auxiliary Air Force squadron best known for its fighter operations during the Second World War, including its role in the Battle of Britain.

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_69ef3557abc481908bf3c146f0f3356a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f626f39064819095a01840684caecc completed May 2, 2026, 4:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3576c1efa881908235f31be28c133c completed June 19, 2026, 5:05 p.m.
NEDg Description generation batch_6a35776bbb3c8190bda2a14ef5abdaf8 completed June 19, 2026, 5:07 p.m.
NED2 Entity disambiguation (via description) batch_6a3577e82568819091390ca6df3cf66e completed June 19, 2026, 5:10 p.m.
Created at: April 27, 2026, 10:56 a.m.