Triple
T17809446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Bavarian Engineers |
E444658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bavarian Army unit |
C39174
|
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: Bavarian Army unit Context triple: [Royal Bavarian Engineers, instanceOf, Bavarian 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.
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.
-
C.
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.
-
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.
Wehrmacht army detachment
A Wehrmacht army detachment was a flexible, temporary German World War II field formation, typically larger than a corps but smaller than a full army, created to control specific operational sectors or ad hoc groupings of units.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:14 a.m.