Triple

T17678165
Position Surface form Disambiguated ID Type / Status
Subject Frankfurt Egelsbach Airport E440691 entity
Predicate IATACode P418 FINISHED
Object QEF 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: QEF | Statement: [Frankfurt Egelsbach Airport, IATACode, QEF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: QEF
Context triple: [Frankfurt Egelsbach Airport, IATACode, QEF]
  • A. QEF chosen
    QEF is the IATA airport code for Frankfurt Egelsbach Airport, a general aviation airfield near Frankfurt, Germany.
  • B. QF
    QF is the IATA airline designator used for Qantas, the flag carrier of Australia.
  • C. QF
    QF is a "qualifying facility" under the U.S. Public Utility Regulatory Policies Act (PURPA), typically a small power producer or cogeneration plant that meets specific efficiency and fuel-use standards to receive certain regulatory benefits.
  • D. EQF
    EQF is a European reference framework that helps compare and translate qualifications across different countries’ education and training systems.
  • E. QFES
    QFES is the primary government agency responsible for fire, rescue, and emergency management services across the Australian state of Queensland.
  • 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_69d8b9e940b081908b862bb0e6e89b0d completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6e959c819092d9d33e79bd51f7 completed April 19, 2026, 6 a.m.
Created at: April 10, 2026, 10:01 a.m.