Triple

T11242371
Position Surface form Disambiguated ID Type / Status
Subject CYVR E266100 entity
Predicate icaoLocationIndicator P419 FINISHED
Object CYVR E266100 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: CYVR | Statement: [CYVR, icaoLocationIndicator, CYVR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CYVR
Context triple: [CYVR, icaoLocationIndicator, CYVR]
  • A. CYVR chosen
    CYVR is the ICAO airport code for Vancouver International Airport, a major Canadian air transport hub located in Richmond, British Columbia.
  • B. CYVQ
    CYVQ is the ICAO airport code for Norman Wells Airport, a regional air transport hub in the Northwest Territories of Canada.
  • C. CYND
    CYND is the ICAO airport code for Gatineau-Ottawa Executive Airport, a regional airport serving the National Capital Region of Canada.
  • D. CYVP
    CYVP is the ICAO airport code for Kuujjuaq Airport, a regional airport serving the community of Kuujjuaq in northern Quebec, Canada.
  • E. CYXD
    CYXD is the former ICAO airport code for Edmonton City Centre Airport, a now-closed airport that once served downtown Edmonton, Alberta, 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_69d6aac656d48190b275efaa7d6074ee completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e91b0b808190bc38008bb344d180 completed April 9, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4cc69402c8190be8785f892a41c7b completed April 19, 2026, 12:36 p.m.
Created at: April 8, 2026, 9:30 p.m.