Triple
T8588065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dingo armored vehicle |
E203357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mine-resistant ambush protected vehicle |
C15354
|
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: mine-resistant ambush protected vehicle Context triple: [Dingo armored vehicle, instanceOf, mine-resistant ambush protected vehicle]
-
A.
mine-resistant ambush-protected vehicle
chosen
A mine-resistant ambush-protected vehicle is a heavily armored, wheeled military vehicle designed to protect occupants from improvised explosive devices, land mines, and ambush attacks.
-
B.
armored utility vehicle
An armored utility vehicle is a heavily protected, multi-purpose transport platform designed to safely carry personnel, equipment, or cargo through hazardous or combat-prone environments.
-
C.
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.
-
D.
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.
-
E.
armored fighting vehicle
An armored fighting vehicle is a heavily protected, mobile combat platform designed to engage enemy forces using integrated weapon systems on land.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.