Triple

T32275382
Position Surface form Disambiguated ID Type / Status
Subject No. 5 Squadron RAF E824528 entity
Predicate garrison P75 FINISHED
Object RAF Farnborough
RAF Farnborough was a historic Royal Air Force station in Hampshire, England, renowned as a major center for British military aviation research, testing, and development.
E2052501 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: RAF Farnborough | Statement: [No. 5 Squadron RAF, garrison, RAF Farnborough]
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: RAF Farnborough
Triple: [No. 5 Squadron RAF, garrison, RAF Farnborough]
Generated description
RAF Farnborough was a historic Royal Air Force station in Hampshire, England, renowned as a major center for British military aviation research, testing, and development.

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_69f3490f404081908450db66884f4334 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bcc425588190afd0dceba43ed79f completed May 3, 2026, 3:11 a.m.
NED1 Entity disambiguation (via context triple) batch_6a35813113908190ad02a2b9a6e4b39e completed June 19, 2026, 5:49 p.m.
NEDg Description generation batch_6a358669e47c8190815192db6dc8cfca completed June 19, 2026, 6:11 p.m.
NED2 Entity disambiguation (via description) batch_6a358ec1398c819096f61833dd9e0add completed June 19, 2026, 6:47 p.m.
Created at: May 1, 2026, 12:43 a.m.