Triple
T12424398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Northern Watch |
E296860
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | no-fly zone enforcement operation |
C14931
|
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: no-fly zone enforcement operation Context triple: [Operation Northern Watch, instanceOf, no-fly zone enforcement operation]
-
A.
airspace security operation
chosen
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.
-
B.
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.
-
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.
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.
-
E.
naval air operation
A naval air operation is a coordinated military action involving aircraft launched from or supported by naval forces to achieve objectives at sea, in the air, or on land.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:55 p.m.