Triple
T6739746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | international civil aviation network |
E154045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation infrastructure network |
C21084
|
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: aviation infrastructure network Context triple: [international civil aviation network, instanceOf, aviation infrastructure network]
-
A.
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.
-
B.
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.
-
C.
business aviation airport
A business aviation airport is a specialized airfield designed primarily to serve private, corporate, and charter aircraft with tailored facilities and services for non-scheduled, business-focused air travel.
-
D.
business aviation airport
A business aviation airport is a specialized airfield designed primarily to serve private, corporate, and charter aircraft with tailored facilities and services for business travelers.
-
E.
private aviation terminal
A private aviation terminal is a specialized airport facility that provides exclusive, streamlined services and amenities for private and corporate aircraft, their passengers, and crews.
- F. None of above. chosen
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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:10 p.m.