Triple

T19777388
Position Surface form Disambiguated ID Type / Status
Subject Barkley Regional Airport E475037 entity
Predicate ICAO code P419 FINISHED
Object KPAH 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: KPAH | Statement: [Barkley Regional Airport, ICAO code, KPAH]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KPAH
Context triple: [Barkley Regional Airport, ICAO code, KPAH]
  • A. KPAH chosen
    KPAH is the ICAO airport code for Barkley Regional Airport, a public airport serving the Paducah, Kentucky area in the United States.
  • B. KPAO
    KPAO is the ICAO airport code for Palo Alto Airport, a busy general aviation facility serving the Palo Alto and greater Silicon Valley area in California.
  • C. KPAE
    KPAE is the ICAO airport code for Paine Field, a public airport in Everett, Washington, known for its proximity to Boeing’s widebody aircraft assembly plant.
  • D. KPA
    KPA is the National Rail station code assigned to Kensington (Olympia) railway station in London.
  • E. Kpase
    Kpase is a dialect of the Fon language spoken by Fon communities in parts of West Africa, particularly in Benin.
  • 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_69d8e51a43a08190956bc6df13c91a77 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65361a8e08190b52944aab25e45fa completed April 20, 2026, 4:25 p.m.
Created at: April 10, 2026, 1:48 p.m.