Triple

T28908159
Position Surface form Disambiguated ID Type / Status
Subject Austrian-Spanish Cooperative Development E733143 entity
Predicate instanceOf P0 FINISHED
Object infantry fighting vehicle family C3288 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: infantry fighting vehicle family
Context triple: [Austrian-Spanish Cooperative Development, instanceOf, infantry fighting vehicle family]
  • A. infantry fighting vehicle chosen
    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.
  • B. military vehicle family
    A military vehicle family is a group of related combat or support vehicles that share a common platform, components, and design philosophy to fulfill different battlefield roles efficiently.
  • C. 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.
  • D. 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.
  • E. improvised fighting vehicle
    An improvised fighting vehicle is a civilian or non-combat vehicle that has been hastily modified with armor, weapons, or other combat enhancements for use in military or paramilitary 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_69f05b096d208190958a57d2e4b5a93a completed April 28, 2026, 7 a.m.
Created at: April 28, 2026, 8:09 a.m.