Triple
T10363703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFRA |
E244196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | restricted 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: restricted airspace Context triple: [SFRA, instanceOf, restricted 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.
airspace security operation
An airspace security operation is a coordinated set of activities, technologies, and procedures designed to monitor, control, and protect designated airspace from unauthorized or hostile aerial threats.
-
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.
military-controlled zone
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, noon