Triple
T17894232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | РВСН |
E447392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Стратегические ракетные войска |
C10845
|
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: Стратегические ракетные войска Context triple: [РВСН, instanceOf, Стратегические ракетные войска]
-
A.
strategic missile force
chosen
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.
-
B.
tactical missile force
A tactical missile force is a military unit or branch equipped and organized to employ short- to medium-range missiles for precise, time-sensitive strikes in support of operational and battlefield objectives.
-
C.
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.
-
D.
directorate of the Ministry of Defense of the USSR
A directorate of the Ministry of Defense of the USSR was a specialized administrative and command body responsible for managing a specific functional area of military policy, operations, or support within the Soviet armed forces.
-
E.
branch of the Armed Forces of the Russian Federation
A branch of the Armed Forces of the Russian Federation is a major organizational component, such as the Ground Forces, Navy, or Aerospace Forces, with specialized roles, capabilities, and structures for conducting military operations.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:19 a.m.