Triple
T33754021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wespe |
E864923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German World War II self-propelled gun |
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: German World War II self-propelled gun Context triple: [Wespe, instanceOf, German World War II self-propelled gun]
-
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.
Karl-Gerät
Karl-Gerät was a series of German World War II self-propelled siege mortars, among the largest artillery pieces ever built, designed to fire massive shells against heavily fortified 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.
Waffen-SS heavy tank battalion
A Waffen-SS heavy tank battalion was a specialized World War II German armored unit equipped primarily with heavy tanks like the Tiger, organized to deliver concentrated breakthrough and counterattack power in support of SS corps and army operations.
-
E.
Panzerjäger unit
A Panzerjäger unit is a specialized military formation equipped and trained primarily for hunting, engaging, and destroying enemy armored vehicles, especially 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.