Triple
T18319654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heathrow Airport expansion projects |
E438836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport expansion program |
C13955
|
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 expansion program Context triple: [Heathrow Airport expansion projects, instanceOf, airport expansion program]
-
A.
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.
-
B.
aviation infrastructure plan
chosen
An aviation infrastructure plan is a strategic blueprint that outlines the development, expansion, maintenance, and integration of airport facilities, airspace systems, and supporting services to safely and efficiently meet current and future air transportation needs.
-
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 under construction
An airport under construction is a partially built air transport facility where runways, terminals, and support infrastructure are actively being developed but not yet operational for regular flight services.
-
E.
airport service program
An airport service program is a coordinated set of services and processes designed to manage and enhance passenger, baggage, and aircraft handling throughout all stages of airport operations.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:36 a.m.