Triple
T20075448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mineta San José International Airport (flight path area) |
E499850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | controlled airspace segment |
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: controlled airspace segment Context triple: [Mineta San José International Airport (flight path area), instanceOf, controlled airspace segment]
-
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.
strategic airspace
Strategic airspace is a designated portion of the sky managed and controlled to support long-term military, security, or national policy objectives, including surveillance, defense, and power projection.
-
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.
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.
-
E.
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.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:40 p.m.