Triple
T18059273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FH77BW L52 Archer prototype |
E432128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | artillery system prototype |
C9295
|
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: artillery system prototype Context triple: [FH77BW L52 Archer prototype, instanceOf, artillery system prototype]
-
A.
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.
-
B.
artillery projectile
An artillery projectile is a munition designed to be fired from large-caliber guns or howitzers, following a ballistic trajectory to deliver destructive, illuminating, or specialized effects on a distant target.
-
C.
truck-mounted artillery system
chosen
A truck-mounted artillery system is a mobile weapons platform that integrates heavy artillery guns or rocket launchers onto a wheeled truck chassis to provide rapid, long-range fire support with high strategic and tactical mobility.
-
D.
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.
-
E.
artillery weapon component
An artillery weapon component is a physical part or subsystem of an artillery piece that contributes to its functions of aiming, loading, firing, stabilizing, or supporting the weapon system.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:26 a.m.