Triple
T18615857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NORAD regional structure |
E455018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air defense command structure |
C698
|
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: air defense command structure Context triple: [NORAD regional structure, instanceOf, air defense command structure]
-
A.
air and missile defence force
An air and missile defence force is a military organization responsible for detecting, tracking, and intercepting hostile aircraft and missiles to protect designated airspace, forces, and critical assets.
-
B.
integrated air defence system
chosen
An integrated air defence system is a coordinated network of sensors, command and control elements, and weapon systems designed to detect, track, and engage aerial threats to protect designated airspace and assets.
-
C.
ground-based air defense system
A ground-based air defense system is a coordinated set of land-deployed sensors, command-and-control elements, and weapon platforms designed to detect, track, and engage airborne threats such as aircraft, missiles, and drones.
-
D.
Air Force organization
An Air Force organization is a structured unit within an air force responsible for planning, directing, and executing air and space operations, support, or administration to achieve military objectives.
-
E.
missile defense command and control system
A missile defense command and control system is an integrated network of sensors, communication links, decision-support tools, and engagement controls that detects, tracks, evaluates, and coordinates responses to missile threats in real time.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.