Triple
T17894545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Navy Strategic Submarine Forces |
E447399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic nuclear forces component |
C34652
|
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: strategic nuclear forces component Context triple: [Russian Navy Strategic Submarine Forces, instanceOf, strategic nuclear forces component]
-
A.
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.
-
B.
strategic nuclear weapon
A strategic nuclear weapon is a high-yield nuclear device designed for long-range delivery against an adversary’s key military, industrial, or political targets to achieve large-scale, war-altering effects.
-
C.
nuclear triad
chosen
A nuclear triad is a nation's three-part strategic nuclear force structure composed of land-based intercontinental ballistic missiles, submarine-launched ballistic missiles, and nuclear-capable strategic bombers, designed to ensure a credible and survivable deterrent.
-
D.
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.
-
E.
nuclear weapons program
A nuclear weapons program is an organized, often state-led effort to research, develop, test, produce, and maintain nuclear warheads and their delivery systems for military deterrence or potential use.
- 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.