Triple

T10664151
Position Surface form Disambiguated ID Type / Status
Subject Memphis International Airport E251306 entity
Predicate ICAO code P419 FINISHED
Object KMEM E251306 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: KMEM | Statement: [Memphis International Airport, ICAO code, KMEM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KMEM
Context triple: [Memphis International Airport, ICAO code, KMEM]
  • A. KMEM chosen
    KMEM is the ICAO airport code for Memphis International Airport, a major cargo and passenger hub in Memphis, Tennessee.
  • B. KMEV
    KMEV is the ICAO airport code for Minden–Tahoe Airport, a public general aviation airport serving the Minden and Lake Tahoe region in Nevada, United States.
  • C. KMCE
    KMCE is the ICAO airport code for Merced Regional Airport, a public airport serving Merced, California.
  • D. KEM
    KEM is the IATA airport code for Kemi-Tornio Airport in northern Finland.
  • E. KEM
    KEM is the National Rail station code for Kemble railway station in Gloucestershire, England.
  • 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_69d6aa5b0d2881909584b20efc5877f0 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6f31e8f5c8190ba03da312d397524 completed April 9, 2026, 12:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69d97a9566e08190a92b49ce73963078 completed April 10, 2026, 10:32 p.m.
Created at: April 8, 2026, 9:08 p.m.