Triple
T20297027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiesel 2 Ozelot |
E505376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | light air-defense vehicle |
C1743
|
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: light air-defense vehicle Context triple: [Wiesel 2 Ozelot, instanceOf, light air-defense vehicle]
-
A.
light armoured vehicle
A light armoured vehicle is a fast, lightly protected military platform designed for reconnaissance, patrol, and troop transport while balancing mobility, protection, and firepower.
-
B.
light attack aircraft variant
A light attack aircraft variant is a modified version of a basic airframe optimized for low-cost, close air support, counterinsurgency, and limited strike missions with reduced payload and simpler systems compared to dedicated attack aircraft.
-
C.
armoured fighting vehicle
chosen
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.
-
D.
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.
-
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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:16 a.m.