Triple

T7062740
Position Surface form Disambiguated ID Type / Status
Subject Akron–Canton Airport E164258 entity
Predicate FAAcode P420 FINISHED
Object CAK E638988 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: CAK | Statement: [Akron–Canton Airport, FAAcode, CAK]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CAK
Context triple: [Akron–Canton Airport, FAAcode, CAK]
  • A. CAK chosen
    CAK is the IATA airport code for Akron–Canton Airport, a commercial airport serving the Akron and Canton region in Ohio, USA.
  • B. KCAK
    KCAK is the ICAO airport code for Akron–Canton Airport, a commercial airport serving the Akron and Canton regions of Ohio, USA.
  • C. KCA
    KCA is a nonprofit organization dedicated to providing life-saving HIV treatment, care, and support to children and families in underserved communities, particularly in Africa and India.
  • D. KAL
    KAL is the ICAO airline designator used to identify Korean Air in international aviation operations.
  • E. CAAC
    CAAC is the acronym for the Civil Aviation Administration of China, the national authority responsible for regulating and overseeing civil aviation in China.
  • 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_69c688796c148190adb2f1596f595f22 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e45cf7488190a7ff15665e283c37 completed March 27, 2026, 8:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7944b4a60819089e565cb895c432f completed March 28, 2026, 8:41 a.m.
Created at: March 27, 2026, 2:38 p.m.