Triple
T20937953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rüdiger von der Goltz |
E515635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Freikorps leader |
C42798
|
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: Freikorps leader Context triple: [Rüdiger von der Goltz, instanceOf, Freikorps leader]
-
A.
Bavarian military officer
A Bavarian military officer is a commissioned leader from the historical Kingdom or modern state of Bavaria, responsible for commanding troops, executing military strategy, and upholding regional and national defense duties within the broader German armed forces context.
-
B.
Nationalist commander
chosen
A nationalist commander is a military leader who directs armed forces in pursuit of a nation-centered political agenda, prioritizing national sovereignty, identity, and interests in strategy and operations.
-
C.
Austro-Hungarian military officer
An Austro-Hungarian military officer was a commissioned leader in the armed forces of the Austro-Hungarian Empire, responsible for commanding troops, implementing imperial military policy, and upholding the dual monarchy’s authority across its diverse territories.
-
D.
Chetnik leader
A Chetnik leader is a commanding figure within the Chetnik movement, responsible for organizing, directing, and representing its military and political activities.
-
E.
Austrian general
An Austrian general is a high-ranking military officer from Austria responsible for planning, directing, and overseeing large-scale military operations and strategic defense initiatives.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:50 p.m.