Triple
T17231688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class B (Washington area) |
E418255
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Class B airspace |
C2156
|
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: Class B airspace Context triple: [Class B (Washington area), instanceOf, Class B airspace]
-
A.
regulated airspace
chosen
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.
-
B.
national airspace
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.
uncontrolled airspace
Uncontrolled airspace is a portion of the atmosphere where air traffic control services are not provided to all aircraft, and pilots are primarily responsible for seeing and avoiding other traffic while following applicable regulations.
-
D.
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.
-
E.
ICAO standard
An ICAO standard is an internationally agreed set of rules, specifications, and recommended practices established by the International Civil Aviation Organization to ensure the safety, regularity, and efficiency of global civil aviation.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:39 a.m.