Triple

T34800674
Position Surface form Disambiguated ID Type / Status
Subject Vancouver–Calgary E1003209 entity
Predicate airCorridorIncludes P5520 FINISHED
Object Vancouver International Airport 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: Vancouver International Airport | Statement: [Vancouver–Calgary, airCorridorIncludes, Vancouver International Airport]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: airCorridorIncludes
Context triple: [Vancouver–Calgary, airCorridorIncludes, Vancouver International Airport]
  • A. appliesToAirspaceOf
    Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
  • B. isGatewayCorridorFor
    Indicates that something serves as a primary access route or passageway enabling movement or connection to another place, system, or area.
  • C. isPartOfCorridorSystem
    Indicates that one entity forms a component or segment within a larger interconnected corridor system.
  • D. hasCorridor chosen
    Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
  • E. nearbyAirportCorridor
    Indicates that an airport corridor is located close to or within a short distance of a given reference location or area.
  • F. None of above.

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_69f76db543808190b188c6c86a91491b completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77a89c4e88190a048e95d42b4a084 completed May 3, 2026, 4:40 p.m.
PD Predicate disambiguation batch_69f7795b1abc8190823664d1caa94649 completed May 3, 2026, 4:35 p.m.
Created at: May 3, 2026, 3:59 p.m.