Triple

T22207242
Position Surface form Disambiguated ID Type / Status
Subject Runway 12R/30L E548844 entity
Predicate airportICAOCode P419 FINISHED
Object LFMT 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: LFMT | Statement: [Runway 12R/30L, airportICAOCode, LFMT]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LFMT
Context triple: [Runway 12R/30L, airportICAOCode, LFMT]
  • A. LFMT chosen
    LFMT is the ICAO airport code for Montpellier–Méditerranée Airport, a regional international airport serving the city of Montpellier in southern France.
  • B. LFMN
    LFMN is the ICAO airport code for Nice Côte d’Azur Airport, a major international airport serving Nice and the French Riviera in southeastern France.
  • C. FLMF
    FLMF is the ICAO airport code for Mfuwe Airport in Zambia, which serves as a key gateway to the South Luangwa National Park.
  • D. LF
    LF is a German vehicle registration code assigned to the Traunstein district in the state of Bavaria.
  • E. LF
    LF is the two-letter IATA airline designator assigned to Contour Airlines, used in flight numbers and ticketing.
  • 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_69e11e3f7e04819089806d81d5ac431e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b2936a481909aa84c7983ed49ee completed April 28, 2026, 9:48 p.m.
Created at: April 16, 2026, 8:36 p.m.