Triple
T5335438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M35 series 2½-ton 6x6 cargo truck |
E123814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tactical truck |
C16027
|
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: tactical truck Context triple: [M35 series 2½-ton 6x6 cargo truck, instanceOf, tactical truck]
-
A.
tactical vehicle
A tactical vehicle is a specialized, often armored, ground transport designed to support military or law-enforcement operations by providing mobility, protection, and mission-specific capabilities in challenging environments.
-
B.
tactical support vehicle
A tactical support vehicle is a specialized, often armored, ground platform designed to transport personnel, equipment, and supplies while providing logistical, communications, and limited defensive capabilities in military or law-enforcement operations.
-
C.
cargo vehicle
chosen
A cargo vehicle is a motorized or non-motorized transport unit designed primarily for carrying goods, materials, or freight rather than passengers.
-
D.
armored recovery vehicle
An armored recovery vehicle is a heavily protected, tracked or wheeled military support vehicle designed to recover, tow, repair, and maintain disabled or damaged armored fighting vehicles on or near the battlefield.
-
E.
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.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2 p.m.