Triple

T19610657
Position Surface form Disambiguated ID Type / Status
Subject Hector International Airport E470720 entity
Predicate ICAO code P419 FINISHED
Object KFAR 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: KFAR | Statement: [Hector International Airport, ICAO code, KFAR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KFAR
Context triple: [Hector International Airport, ICAO code, KFAR]
  • A. KFAR chosen
    KFAR is the ICAO airport code for Hector International Airport, a public airport serving Fargo, North Dakota, in the United States.
  • B. KAF
    KAF is the Kenya Air Force, the aerial warfare branch of the Kenya Defence Forces responsible for defending Kenyan airspace and providing air support to military operations.
  • C. KFA
    KFA is the commonly used abbreviation for the Korea Football Association, the governing body of football in South Korea.
  • D. KÄR
    KÄR is the common abbreviation for Oulun Kärpät, a prominent professional ice hockey club based in Oulu, Finland.
  • E. KAR
    KAR is the commonly used abbreviation for the King's African Rifles, a former multi-battalion British colonial regiment recruited from East Africa.
  • 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_69d8e510fa248190b7afb274a1d4cf73 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e640cb180c8190ba96ffb69c24e2e1 completed April 20, 2026, 3:05 p.m.
Created at: April 10, 2026, 1:43 p.m.