Triple
T26266306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Army on the Western Front |
E656991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of Imperial German Army |
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: component of Imperial German Army Context triple: [German Army on the Western Front, instanceOf, component of Imperial German Army]
-
A.
branch of the German Army
A branch of the German Army is a specialized organizational subdivision responsible for a distinct set of military functions, capabilities, and operational roles within the overall land forces structure.
-
B.
component of the Prussian Army
A component of the Prussian Army is an organizational subdivision—such as a regiment, corps, or specialized unit—responsible for specific military functions within the broader Prussian military structure.
-
C.
component of the Bavarian Army
A component of the Bavarian Army is an organizational subdivision—such as a unit, formation, or support element—responsible for specific military functions within Bavaria’s land 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.
branch of the Bundeswehr
A branch of the Bundeswehr is a major organizational component of Germany’s armed forces, such as the Army, Navy, or Air Force, each with distinct roles, capabilities, and responsibilities in national defense.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
Created at: April 26, 2026, 9:11 p.m.