Triple
T6659882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German 1st Parachute Division |
E151447
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fallschirmjäger division |
C3680
|
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: Fallschirmjäger division Context triple: [German 1st Parachute Division, instanceOf, Fallschirmjäger division]
-
A.
airborne infantry division
chosen
An airborne infantry division is a large military formation of specially trained soldiers equipped and organized to deploy rapidly by air, typically via parachute or air assault, to seize and hold key objectives behind enemy lines.
-
B.
Wehrmacht infantry division
A Wehrmacht infantry division was a World War II-era German Army formation composed primarily of foot soldiers, supported by artillery, engineers, and logistical units, organized for sustained ground combat operations.
-
C.
Wehrmacht corps
A Wehrmacht corps was a mid-level German Army formation in World War II, typically commanding several divisions and supporting units to conduct coordinated operations within a larger army structure.
-
D.
parachute infantry regiment
A parachute infantry regiment is a military unit composed of soldiers trained and equipped to deploy by parachute into combat zones to conduct airborne assault, seizure, and holding of key objectives behind enemy lines.
-
E.
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.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:02 p.m.