Triple
T1018581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Airspace System governance |
E21988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation regulatory framework |
C5730
|
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 regulatory framework Context triple: [National Airspace System governance, instanceOf, aviation regulatory framework]
-
A.
aviation authority
An aviation authority is a governmental or regulatory body responsible for overseeing civil aviation safety, security, standards, and compliance within a specific jurisdiction.
-
B.
civil aircraft registration
Civil aircraft registration is the unique alphanumeric identifier assigned by a national aviation authority to an aircraft, linking it to a specific country and its official registry for legal, operational, and safety purposes.
-
C.
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.
-
D.
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.
-
E.
aircraft registration
An aircraft registration is a unique alphanumeric identifier assigned by a national aviation authority to an individual aircraft for legal, operational, and tracking purposes.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.