Triple
T16741097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASLAV-R |
E406834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | recovery vehicle variant |
C13989
|
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: recovery vehicle variant Context triple: [ASLAV-R, instanceOf, recovery vehicle variant]
-
A.
armored recovery vehicle
chosen
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.
-
B.
pickup truck variant
A pickup truck variant is a specific configuration or model of a pickup truck that differs in features such as cab style, bed length, drivetrain, payload capacity, or trim level to suit particular use cases or customer preferences.
-
C.
HMMWV variant
A HMMWV variant is a specific configuration or modification of the High Mobility Multipurpose Wheeled Vehicle tailored for distinct operational roles, capabilities, or mission requirements.
-
D.
Humvee variant
A Humvee variant is a specific configuration of the High Mobility Multipurpose Wheeled Vehicle (HMMWV) tailored with distinct equipment, armor, or mission-specific modifications to fulfill particular operational roles.
-
E.
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.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.