Triple
T23879147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-Jagdverbände |
E600150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Waffen-SS special operations unit |
C48162
|
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: Waffen-SS special operations unit Context triple: [SS-Jagdverbände, instanceOf, Waffen-SS special operations unit]
-
A.
Waffen-SS regiment
A Waffen-SS regiment is a military unit of the Nazi Party’s armed wing, typically composed of several battalions, that served as a frontline combat formation during World War II and was often involved in both conventional warfare and war crimes.
-
B.
Waffen-SS corps
The Waffen-SS corps was the combat branch of Nazi Germany’s SS organization, comprising ideologically driven, militarized units that fought alongside the regular army and were heavily involved in war crimes and atrocities during World War II.
-
C.
Waffen-SS division
A Waffen-SS division was a large, front-line combat formation of Nazi Germany’s Waffen-SS, combining infantry, armor, and support units under a unified command and ideologically aligned with the SS.
-
D.
Waffen-SS field army
A Waffen-SS field army was a large, front-line combat formation of Nazi Germany’s Waffen-SS, composed of multiple corps and divisions and employed in major operational campaigns during World War II.
-
E.
Waffen-SS battle group
A Waffen-SS battle group was an ad hoc, mixed-arms combat formation of the Nazi SS, assembled from available units and resources for specific tactical operations during World War II.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:23 p.m.