Triple

T21555099
Position Surface form Disambiguated ID Type / Status
Subject RAF Germany E531869 entity
Predicate garrison P75 FINISHED
Object RAF Brüggen NE NERFINISHED

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 Brüggen | Statement: [RAF Germany, garrison, RAF Brüggen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RAF Brüggen
Context triple: [RAF Germany, garrison, RAF Brüggen]
  • A. RAF Brüggen chosen
    RAF Brüggen was a major Royal Air Force station in Germany that served as a key Cold War base for strike and reconnaissance aircraft operating in Europe.
  • B. RAF Laarbruch
    RAF Laarbruch was a former Royal Air Force station in Germany that served as a key Cold War base for various RAF squadrons and NATO operations.
  • C. RAF Gutersloh
    RAF Gutersloh was a Royal Air Force station in West Germany that served as a key Cold War airbase for British fighter and reconnaissance squadrons.
  • D. RAF Wildenrath
    RAF Wildenrath was a former Royal Air Force station in West Germany that served as a key Cold War base for British air defense and strike aircraft.
  • E. RAF Germany
    RAF Germany was the Royal Air Force’s forward-deployed command in West Germany during the Cold War, operating combat aircraft and supporting NATO’s air defense and strike missions in Central Europe.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eed2de1c248190b303a4a55b022374 completed April 27, 2026, 3:07 a.m.
Created at: April 16, 2026, 6:29 p.m.