Triple
T15882111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 32nd Army Air and Missile Defense Command |
E385097
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | missile defense command |
C26426
|
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: missile defense command Context triple: [32nd Army Air and Missile Defense Command, instanceOf, missile defense command]
-
A.
missile defense brigade
A missile defense brigade is a military unit responsible for detecting, tracking, and intercepting incoming missile threats to protect designated forces, assets, and territories.
-
B.
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.
-
C.
missile defense program
A missile defense program is an organized system of technologies, policies, and operations designed to detect, track, intercept, and neutralize incoming missiles before they reach their intended targets.
-
D.
air and missile defence force
chosen
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.
-
E.
strategic missile force
A strategic missile force is a military organization equipped with long-range, often nuclear-capable missiles designed to deter adversaries and conduct deep-strike operations against high-value strategic targets.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.