Triple
T13422681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wespe self-propelled howitzer |
E313396
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II German self-propelled artillery |
C29127
|
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: World War II German self-propelled artillery Context triple: [Wespe self-propelled howitzer, instanceOf, World War II German self-propelled artillery]
-
A.
World War II armoured fighting vehicle
chosen
A World War II armoured fighting vehicle is a tracked or wheeled, armored, and typically armed military vehicle designed and used between 1939 and 1945 for frontline combat, support, or reconnaissance roles.
-
B.
155 mm artillery piece
A 155 mm artillery piece is a large-caliber, long-range field gun or howitzer designed to deliver powerful indirect fire support using 155 millimeter projectiles against distant targets.
-
C.
self-propelled howitzer variant
A self-propelled howitzer variant is an armored, mobile artillery platform built on a powered chassis that modifies a base howitzer design for specific roles such as increased firepower, protection, mobility, or specialized mission capabilities.
-
D.
155 mm howitzer
A 155 mm howitzer is a large-caliber, towed or self-propelled artillery piece designed to fire heavy shells at long ranges in high-arcing trajectories for indirect fire support.
-
E.
anti-tank gun
An anti-tank gun is a ground-based artillery weapon designed to fire high-velocity projectiles capable of penetrating and destroying armored vehicles, particularly tanks.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:39 p.m.