Triple
T16353236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AS-90 tracked chassis |
E397109
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | self-propelled artillery chassis |
C18935
|
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: self-propelled artillery chassis Context triple: [AS-90 tracked chassis, instanceOf, self-propelled artillery chassis]
-
A.
self-propelled howitzer variant
chosen
A self-propelled howitzer variant is an armored, mobile artillery platform built on a powered chassis that modifies a base howitzer design for specific roles such as increased firepower, protection, mobility, or specialized mission capabilities.
-
B.
truck-mounted artillery system
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.
-
C.
military engineering vehicle
A military engineering vehicle is a specialized armored or unarmored platform designed to support combat operations by performing construction, demolition, obstacle breaching, and battlefield mobility or survivability tasks.
-
D.
armored vehicle
An armored vehicle is a heavily protected, often weaponized, transport platform designed to safeguard occupants and critical equipment against ballistic, explosive, and chemical threats in hostile environments.
-
E.
armored military vehicle
An armored military vehicle is a heavily protected, often weaponized, ground transport designed to carry personnel or equipment safely through hostile environments.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.