Triple
T27086567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smerch |
E686049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multiple rocket launcher system |
C12692
|
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: multiple rocket launcher system Context triple: [Smerch, instanceOf, multiple rocket launcher system]
-
A.
multiple rocket launcher
chosen
A multiple rocket launcher is a mobile artillery system equipped with several rocket tubes or rails that can fire multiple unguided or guided rockets in rapid succession to deliver concentrated firepower over a wide area.
-
B.
counter-rocket artillery and mortar system
A counter-rocket, artillery, and mortar (C-RAM) system is an integrated defensive weapon system designed to detect, track, and intercept incoming rockets, artillery shells, and mortar rounds in real time to protect designated areas and assets.
-
C.
missile launch system
A missile launch system is an integrated hardware and software framework that prepares, arms, targets, and fires missiles while managing safety, authorization, and trajectory control.
-
D.
road-mobile missile system
A road-mobile missile system is a transportable weapons platform mounted on wheeled or tracked vehicles that can move, deploy, and launch missiles from various locations to enhance survivability and operational flexibility.
-
E.
military rocket
A military rocket is a self-propelled, unguided or guided weapon system that uses rocket propulsion to deliver explosive or specialized payloads to a target for combat or strategic purposes.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:38 a.m.