Triple
T16137484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5th Mechanized Corps |
E391569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet mechanized corps |
C13721
|
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: Soviet mechanized corps Context triple: [5th Mechanized Corps, instanceOf, Soviet mechanized corps]
-
A.
Soviet field army
A Soviet field army was a large, operational-level military formation of the Soviet Armed Forces, typically comprising multiple corps or divisions, support units, and command structures, organized to conduct sustained offensive or defensive campaigns in a designated theater of operations.
-
B.
armoured corps
chosen
An armoured corps is a large military formation composed primarily of tank and mechanized units, designed to deliver rapid, heavily protected offensive and defensive ground operations.
-
C.
Wehrmacht corps
A Wehrmacht corps was a mid-level German Army formation in World War II, typically commanding several divisions and supporting units to conduct coordinated operations within a larger army structure.
-
D.
U.S. Army armored division
A U.S. Army armored division is a large, combined-arms military formation centered on tanks and mechanized infantry, designed to conduct high-intensity, mobile ground combat operations.
-
E.
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.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:01 a.m.