Triple
T27126030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German 9th Army |
E681433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial German Army unit |
C51345
|
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: Imperial German Army unit Context triple: [German 9th Army, instanceOf, Imperial German Army unit]
-
A.
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.
-
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.
component of Imperial German Army
chosen
A component of the Imperial German Army is an organizational unit—such as a regiment, corps, or specialized branch—that collectively contributed to the structure, operations, and capabilities of Germany’s land forces during the Imperial era (1871–1918).
-
D.
Wehrmacht regiment
A Wehrmacht regiment was a mid-level military unit of Nazi Germany’s armed forces, typically composed of several battalions and supporting elements, responsible for tactical operations within a division.
-
E.
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.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:01 a.m.