Triple
T28097123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway D |
E710123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airfield infrastructure |
C2678
|
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: airfield infrastructure Context triple: [Runway D, instanceOf, airfield infrastructure]
-
A.
airfield
An airfield is a designated area of land equipped with runways, taxiways, and minimal support facilities for the takeoff, landing, and ground movement of aircraft.
-
B.
airport infrastructure project
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.
-
C.
airport runway
chosen
An airport runway is a long, specially prepared strip of land or pavement where aircraft take off and land, designed with specific markings, lighting, and surface strength to ensure safe operations.
-
D.
aviation infrastructure network
An aviation infrastructure network is an interconnected system of airports, airways, navigation aids, communication systems, and support facilities that collectively enable the safe, efficient movement of aircraft and passengers.
-
E.
aviation infrastructure plan
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.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 9:02 p.m.