Triple

T31501692
Position Surface form Disambiguated ID Type / Status
Subject RAF Tern Hill E803701 entity
Predicate hasResidentUnit P203367 FINISHED
Object No. 50 Group RAF
No. 50 Group RAF was a Royal Air Force formation responsible for overseeing and coordinating flying training units in the United Kingdom during the Second World War.
E2050479 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. 50 Group RAF | Statement: [RAF Tern Hill, hasResidentUnit, No. 50 Group 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. 50 Group RAF
Triple: [RAF Tern Hill, hasResidentUnit, No. 50 Group RAF]
Generated description
No. 50 Group RAF was a Royal Air Force formation responsible for overseeing and coordinating flying training units in the United Kingdom 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_69f348cae52081909fa8e5f697523ae3 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a016d254eec81908a60e8d26bab9d24 completed May 11, 2026, 5:46 a.m.
NED1 Entity disambiguation (via context triple) batch_6a35812eb9048190851cbe7e71ad5623 completed June 19, 2026, 5:49 p.m.
NEDg Description generation batch_6a3581ddeab88190b15f2f974ef67e0e completed June 19, 2026, 5:52 p.m.
NED2 Entity disambiguation (via description) batch_6a3582372b908190be6d6197e7e4ea92 completed June 19, 2026, 5:53 p.m.
Created at: April 30, 2026, 9:44 p.m.