Triple

T27295171
Position Surface form Disambiguated ID Type / Status
Subject No. 141 Squadron RAF E688741 entity
Predicate garrison P75 FINISHED
Object RAF Scorton
RAF Scorton was a Royal Air Force station in North Yorkshire, England, that served as a base for various fighter and training units, particularly during the Second World War.
E1940639 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 Scorton | Statement: [No. 141 Squadron RAF, garrison, RAF Scorton]
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 Scorton
Triple: [No. 141 Squadron RAF, garrison, RAF Scorton]
Generated description
RAF Scorton was a Royal Air Force station in North Yorkshire, England, that served as a base for various fighter and training units, particularly 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_69ef355a96308190a2bed991525fb278 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f6277f37208190a33476a7a3bddec6 completed May 2, 2026, 4:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28fb843dc88190bc6b421c9ed6fde1 completed June 10, 2026, 5:52 a.m.
NEDg Description generation batch_6a28ffc3037481909e380c0b60ebce5c completed June 10, 2026, 6:10 a.m.
NED2 Entity disambiguation (via description) batch_6a29005bb6bc81909fa20caeb92ac2be completed June 10, 2026, 6:12 a.m.
Created at: April 27, 2026, 11:18 a.m.