Triple
T22380669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary International Airport terminal projects |
E553263
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport terminal expansion program |
C44526
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: airport terminal expansion program Context triple: [Calgary International Airport terminal projects, instanceOf, airport terminal expansion program]
-
A.
airport infrastructure project
chosen
An airport infrastructure project is a coordinated set of planning, design, construction, and upgrade activities aimed at developing or improving airport facilities, systems, and services to support safe, efficient air transportation.
-
B.
airport infrastructure funding program
An airport infrastructure funding program is a structured initiative that allocates financial resources to plan, build, upgrade, and maintain airport facilities and related systems to ensure safe, efficient, and sustainable air transportation operations.
-
C.
airport system
An airport system is an integrated network of facilities, services, and processes that manages the safe, efficient movement of passengers, cargo, and aircraft within and around an airport.
-
D.
airport-related building
A building located on or near an airport that supports air travel operations, such as terminals, control towers, hangars, or maintenance facilities.
-
E.
Airport
An airport is a complex transportation hub where aircraft take off, land, are serviced, and passengers and cargo transition between air and ground travel through various terminals and support facilities.
- F. None of above.
Provenance (1 batch)
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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.