Triple

T19987318
Position Surface form Disambiguated ID Type / Status
Subject Yakima Air Terminal E493967 entity
Predicate hasFAAIdentifier P420 FINISHED
Object YKM 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: YKM | Statement: [Yakima Air Terminal, hasFAAIdentifier, YKM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: YKM
Context triple: [Yakima Air Terminal, hasFAAIdentifier, YKM]
  • A. YKM chosen
    YKM is the IATA airport code for Yakima Air Terminal, a public airport serving Yakima, Washington, United States.
  • B. KYKM
    KYKM is the ICAO airport code for Yakima Air Terminal, a public airport serving Yakima, Washington.
  • C. FYKM
    FYKM is the ICAO airport code assigned to Katima Mulilo Airport in Namibia.
  • D. WKM
    WKM is the abbreviated name for the Warszawska Karta Miejska, Warsaw’s electronic public transport card used for storing and validating tickets.
  • E. WKM
    WKM is the National Rail station code for Wokingham railway station in Berkshire, England.
  • 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65fdd1a5c8190af756632aac38bf4 completed April 20, 2026, 5:18 p.m.
Created at: April 11, 2026, 3:29 p.m.