Triple
T32411803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian corps under Riesch |
E828241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austrian corps |
C60434
|
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: Austrian corps Context triple: [Austrian corps under Riesch, instanceOf, Austrian corps]
-
A.
Prussian Army corps
A Prussian Army corps was a large, semi-independent military formation within the Prussian Army, typically composed of multiple divisions and supporting units, organized for operational-level command and control in war.
-
B.
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.
-
C.
Hessian brigade
A Hessian brigade is a military unit composed of German auxiliary troops from the state of Hesse, historically hired by foreign powers—most notably Britain during the American Revolutionary War—to fight as organized infantry formations.
-
D.
Austrian military personnel
Austrian military personnel are individuals who serve or have served in the armed forces of Austria, including its historical predecessors, in various military roles and capacities.
-
E.
Freikorps unit
A Freikorps unit is a semi-autonomous, often nationalist paramilitary formation composed largely of ex-soldiers, operating with limited state oversight in post–World War I Germany to combat perceived internal and external enemies.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.