Triple
T16680028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-RAM |
E405314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | counter-rocket artillery and mortar system |
C38229
|
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: counter-rocket artillery and mortar system Context triple: [C-RAM, instanceOf, counter-rocket artillery and mortar system]
-
A.
artillery rocket
An artillery rocket is an unguided or minimally guided rocket-propelled munition launched from ground-based systems to deliver explosive warheads over long ranges in support of military fire missions.
-
B.
multiple rocket launcher
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.
-
C.
self-propelled siege mortar
A self-propelled siege mortar is a heavily armored, mobile artillery platform mounting a large-caliber, high-arc mortar designed to advance with or behind frontline forces and deliver powerful indirect fire against fortified positions.
-
D.
anti-tank gun
An anti-tank gun is a ground-based artillery weapon designed to fire high-velocity projectiles capable of penetrating and destroying armored vehicles, particularly tanks.
-
E.
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.
- F. None of above. chosen
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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.