Triple

T18615695
Position Surface form Disambiguated ID Type / Status
Subject 17 Wing Winnipeg E455014 entity
Predicate hasIcaoCode P419 FINISHED
Object CYWG 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: CYWG | Statement: [17 Wing Winnipeg, hasIcaoCode, CYWG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CYWG
Context triple: [17 Wing Winnipeg, hasIcaoCode, CYWG]
  • A. CYWG chosen
    CYWG is the ICAO airport code for Winnipeg James Armstrong Richardson International Airport, the primary commercial airport serving Winnipeg, Manitoba, Canada.
  • B. YWG
    YWG is the IATA airport code for Winnipeg James Armstrong Richardson International Airport, the primary commercial airport serving Winnipeg, Manitoba, Canada.
  • C. CYCG
    CYCG is the ICAO airport code for West Kootenay Regional Airport in British Columbia, Canada.
  • D. CYWK
    CYWK is the ICAO airport code for Labrador City Airport in Newfoundland and Labrador, Canada.
  • E. YSWG
    YSWG is the ICAO airport code for Wagga Wagga Airport, a regional airport serving Wagga Wagga in New South Wales, Australia.
  • 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_69d8d38bbe7c8190bdec3138e7d413c9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54d04bdc48190b0213132923a7580 completed April 19, 2026, 9:45 p.m.
Created at: April 10, 2026, 11:45 a.m.