Triple

T17360291
Position Surface form Disambiguated ID Type / Status
Subject Victoria Inner Harbour Airport E422049 entity
Predicate hasIATAcode P2569 FINISHED
Object YWH NE ONNED1

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: YWH | Statement: [Victoria Inner Harbour Airport, hasIATAcode, YWH]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: YWH
Context triple: [Victoria Inner Harbour Airport, hasIATAcode, YWH]
  • A. YWH chosen
    YWH is the IATA airport code for Victoria Inner Harbour Airport, a seaplane base serving downtown Victoria, British Columbia, Canada.
  • B. FYWH
    FYWH is the ICAO airport code for Hosea Kutako International Airport, the main international gateway serving Windhoek, Namibia.
  • C. YWK
    YWK is the IATA airport code for Labrador City Airport in Newfoundland and Labrador, Canada.
  • D. YWB
    YWB is the IATA airport code for Kangiqsujuaq Airport, a small regional airport serving the Inuit community of Kangiqsujuaq in northern Quebec, Canada.
  • E. YWL
    YWL is the IATA airport code for Williams Lake Regional Airport serving the city of Williams Lake in British Columbia, Canada.
  • 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_69d889d520008190a26917a95bf1c2ea completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a4cacd881909fd722068b019f25 completed April 19, 2026, 2:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01955e4cb481909e3193439bb85cd8 in_progress May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:44 a.m.