Triple
T38457613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panzerkampfwagen VI Ausf. E |
E912361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tiger I |
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: Tiger I Context triple: [Panzerkampfwagen VI Ausf. E, instanceOf, Tiger I]
-
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.
Derfflinger-class battlecruiser
The Derfflinger-class battlecruiser was a group of German Imperial Navy capital ships of World War I that combined heavy armament and relatively high speed with improved armor protection compared to earlier German battlecruisers.
-
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.
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.
Scharnhorst-class battleship
The Scharnhorst-class battleship was a pair of fast, heavily armed German capital ships built in the late 1930s that combined relatively light main guns with strong armor and high speed for commerce raiding and fleet actions in World War II.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.