Triple

T7156175
Position Surface form Disambiguated ID Type / Status
Subject RAF Fairford E166816 entity
Predicate IATA code P2569 FINISHED
Object FFD E166816 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: FFD | Statement: [RAF Fairford, IATA code, FFD]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FFD
Context triple: [RAF Fairford, IATA code, FFD]
  • A. FFD chosen
    FFD is the IATA airport code for RAF Fairford, a Royal Air Force station in Gloucestershire, England, used by both the UK and United States air forces and known for hosting major airshows.
  • B. FFC
    FFC is the commonly used abbreviation for Falkirk Football Club, a professional Scottish football team based in Falkirk.
  • C. FFC
    FFC is the common abbreviation for Fluminense Football Club, a traditional Brazilian sports club best known for its professional football team based in Rio de Janeiro.
  • D. FFS
    FFS is the commonly used abbreviation for the Swiss Federal Railways, the national railway company of Switzerland.
  • E. FFM
    FFM is an abbreviation commonly used for the Montreal World Film Festival, an international film festival held annually in Montreal, Canada.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c68887a5cc8190bec0ea96227164f7 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e80dafdc8190b24863b83f084d12 completed March 27, 2026, 8:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7b8f42abc8190856210b8dea0a6de completed March 28, 2026, 11:18 a.m.
Created at: March 27, 2026, 2:47 p.m.