Triple
T18492015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajax tracked chassis |
E451840
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military vehicle platform |
C15396
|
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: military vehicle platform Context triple: [Ajax tracked chassis, instanceOf, military vehicle platform]
-
A.
armored military vehicle
chosen
An armored military vehicle is a heavily protected, often weaponized, ground transport designed to carry personnel or equipment safely through hostile environments.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
military vehicle category
A military vehicle category is a classification grouping that organizes military vehicles based on their roles, capabilities, and design characteristics, such as combat, transport, reconnaissance, or support functions.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:35 a.m.