Triple
T33666508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geschützwagen Tiger (Grille 17/21) |
E862507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German self-propelled artillery vehicle project |
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 self-propelled artillery vehicle project Context triple: [Geschützwagen Tiger (Grille 17/21), instanceOf, German self-propelled artillery vehicle project]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
armored vehicle development program
A coordinated, multi-phase initiative that manages the research, design, testing, production, and fielding of new or upgraded armored combat vehicles to meet defined military requirements.
-
E.
German military equipment
German military equipment encompasses the weapons, vehicles, gear, and support systems designed, produced, or used by German armed forces across different historical periods.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.