Triple
T29059153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IV. Armeekorps |
E735476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian Army corps |
C54658
|
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: Prussian Army corps Context triple: [IV. Armeekorps, instanceOf, Prussian Army corps]
-
A.
Prussian Army regiment
A Prussian Army regiment is a military unit of the Kingdom of Prussia, typically composed of several battalions or squadrons, organized under a unified command structure for tactical, administrative, and ceremonial purposes.
-
B.
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.
-
C.
Bavarian Army unit
A Bavarian Army unit is a military formation originating from the Kingdom or State of Bavaria, organized for combat, support, or administrative roles within the broader structure of the Bavarian or German armed forces.
-
D.
German Army regiment
A German Army regiment is a mid-sized military unit typically composed of several battalions, providing a structured formation for combat, support, and administrative functions within the German land forces.
-
E.
German field army
A German field army is a large, operational-level military formation of the German armed forces, typically composed of multiple corps and supporting units, organized to conduct sustained land campaigns in a defined theater of war.
- F. None of above. chosen
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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:14 a.m.