Triple

T27266220
Position Surface form Disambiguated ID Type / Status
Subject RAF Ford E687910 entity
Predicate hostedUnit P3556 FINISHED
Object No. 184 Squadron RAF
No. 184 Squadron RAF was a Royal Air Force fighter-bomber unit active during the Second World War, known for operating Hawker Typhoons in ground-attack and close air support roles.
E2063832 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. 184 Squadron RAF | Statement: [RAF Ford, hostedUnit, No. 184 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. 184 Squadron RAF
Triple: [RAF Ford, hostedUnit, No. 184 Squadron RAF]
Generated description
No. 184 Squadron RAF was a Royal Air Force fighter-bomber unit active during the Second World War, known for operating Hawker Typhoons in ground-attack and close air support roles.

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_6a363c6a7d8c81909089eab80a8aaa46 completed June 20, 2026, 7:08 a.m.
NEDg Description generation batch_6a364ba0f2a08190a4a52f9d32829a9f completed June 20, 2026, 8:13 a.m.
NED2 Entity disambiguation (via description) batch_6a364c67a6bc8190a2c149406910a337 completed June 20, 2026, 8:16 a.m.
Created at: April 27, 2026, 10:56 a.m.