Triple
T2229267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Airspace System |
E48726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airspace system |
C2155
|
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: airspace system Context triple: [National Airspace System, instanceOf, airspace system]
-
A.
airspace governance framework
An airspace governance framework is a structured set of policies, regulations, and institutional arrangements that define how airspace is allocated, managed, monitored, and enforced to ensure safe, efficient, and equitable use by all airspace users.
-
B.
national airspace
chosen
National airspace is the three-dimensional region of the atmosphere above a country's territory and territorial waters over which that nation exercises legal jurisdiction, regulation, and control of aircraft operations.
-
C.
regulated airspace
Regulated airspace is a defined volume of the atmosphere where aircraft operations are subject to specific rules, restrictions, and oversight by aviation authorities to ensure safety and orderly traffic flow.
-
D.
air navigation organization
An air navigation organization is an entity responsible for planning, managing, and controlling the safe and efficient movement of aircraft through designated airspace using air traffic services, communication, navigation, and surveillance systems.
-
E.
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.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:47 p.m.