Triple
T27687203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Tiger VK 45.01(P) |
E698063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German heavy tank prototype |
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 heavy tank prototype Context triple: [Porsche Tiger VK 45.01(P), instanceOf, German heavy tank prototype]
-
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.
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.
-
D.
German armoured formation
A German armoured formation is a military unit or grouping, typically at battalion, regiment, brigade, or division level, built around tanks and other armored fighting vehicles to conduct rapid, mechanized offensive and defensive operations.
-
E.
main battle tank
A main battle tank is a heavily armored, highly mobile, front-line combat vehicle that combines powerful direct-fire weaponry with advanced protection and maneuverability to dominate ground engagements.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:50 p.m.