Triple

T18974941
Position Surface form Disambiguated ID Type / Status
Subject Halifax Stanfield International Airport E464270 entity
Predicate ICAO code P419 FINISHED
Object CYHZ 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: CYHZ | Statement: [Halifax Stanfield International Airport, ICAO code, CYHZ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CYHZ
Context triple: [Halifax Stanfield International Airport, ICAO code, CYHZ]
  • A. CYHZ chosen
    CYHZ is the ICAO airport code for Halifax Stanfield International Airport, the primary commercial airport serving Halifax and much of Atlantic Canada.
  • B. YHZ
    YHZ is the IATA airport code for Halifax Stanfield International Airport, the primary commercial airport serving Halifax and much of Atlantic Canada.
  • C. CYZF
    CYZF is the ICAO airport code for Yellowknife Airport, a major aviation hub serving the capital of Canada's Northwest Territories.
  • D. CYXH
    CYXH is the ICAO airport code for Medicine Hat Regional Airport in Alberta, Canada.
  • E. CYHD
    CYHD is the ICAO airport code for Dryden Regional Airport in Dryden, Ontario, Canada.
  • 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_69d8dd008af48190a97ff1c6488edf1b completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d61e71988190817cada25672a1ce completed April 20, 2026, 7:30 a.m.
Created at: April 10, 2026, noon