Triple
T32403691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 35th Air Defense Artillery Brigade |
E828019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air and missile defense unit |
C19966
|
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 and missile defense unit Context triple: [35th Air Defense Artillery Brigade, instanceOf, air and missile defense unit]
-
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.
missile defense brigade
chosen
A missile defense brigade is a military unit responsible for detecting, tracking, and intercepting incoming missile threats to protect designated forces, assets, and territories.
-
C.
surface-to-air missile wing
A surface-to-air missile wing is a military aviation unit responsible for operating, maintaining, and coordinating ground-based missile systems designed to detect, track, and engage airborne threats.
-
D.
air and missile defense interceptor
An air and missile defense interceptor is a guided weapon system designed to detect, track, and destroy incoming aircraft, cruise missiles, or ballistic missiles before they reach their targets.
-
E.
integrated air defence system
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.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.