Triple

T14929383
Position Surface form Disambiguated ID Type / Status
Subject Runway 06/24 E372217 entity
Predicate airportIATACode P418 FINISHED
Object EDI E270332 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: EDI | Statement: [Runway 06/24, airportIATACode, EDI]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EDI
Context triple: [Runway 06/24, airportIATACode, EDI]
  • A. EDI chosen
    EDI is the three-letter IATA airport code for Edinburgh Airport, the main international airport serving Scotland’s capital city.
  • B. EDI
    EDI is the official abbreviation for the Swiss Federal Department of Home Affairs, a key government ministry responsible for social security, health, culture, and related domestic affairs.
  • C. IDOC
    IDOC is the state agency responsible for overseeing prisons, community-based corrections, and offender rehabilitation in Iowa.
  • D. IDOC
    IDOC is the state agency responsible for overseeing prisons, parole, and related correctional services in Illinois.
  • E. ESB
    ESB is the vehicle registration code used on license plates for the Neustadt an der Waldnaab district in Bavaria, Germany.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded634e67881909daec9eaef188d09 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe72c728948190a1cfc62f4038b6ec completed May 8, 2026, 11:33 p.m.
Created at: April 10, 2026, 2:36 a.m.