Triple

T4213816
Position Surface form Disambiguated ID Type / Status
Subject Bushmaster Protected Mobility Vehicle E93966 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: [Bushmaster Protected Mobility Vehicle, instanceOf, mine-resistant ambush-protected vehicle]
  • A. 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.
  • B. armoured fighting vehicle
    An armoured fighting vehicle is a heavily protected, mobile combat platform—typically tracked or wheeled—designed to engage enemy forces using integrated weapons systems on the battlefield.
  • C. 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.
  • D. amphibious vehicle
    An amphibious vehicle is a transport vehicle designed to operate efficiently on both land and water by seamlessly transitioning between driving and floating or sailing modes.
  • E. infantry fighting vehicle
    An infantry fighting vehicle is a heavily armed and armored combat vehicle designed to transport infantry into battle while providing direct fire support and protection on the battlefield.
  • F. None of above. chosen

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_69b3451743608190808f41d17ccf2650 completed March 12, 2026, 10:58 p.m.
Created at: March 12, 2026, 11:04 p.m.