Triple
T21773133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiwis |
E537485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II auxiliary units |
C26842
|
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: World War II auxiliary units Context triple: [Hiwis, instanceOf, World War II auxiliary units]
-
A.
World War II special forces
World War II special forces were elite, highly trained military units from various nations that conducted covert, high-risk operations such as sabotage, reconnaissance, and raids behind enemy lines to achieve strategic objectives.
-
B.
World War II unit in fiction
A World War II unit in fiction is a narrative-focused military group, real or imagined, whose members, missions, and relationships are used to explore the human and strategic dimensions of the Second World War within a fictional story.
-
C.
World War II supply line
A World War II supply line is the network of transportation routes, logistics operations, and support infrastructure used to move troops, equipment, fuel, and provisions to and from battlefronts during the war.
-
D.
World War II civilian group
A World War II civilian group is a collective of non-military individuals organized for purposes such as resistance, support, survival, or collaboration within the social, political, and economic upheavals of the war.
-
E.
participants in World War II
chosen
Participants in World War II are the nations, military forces, resistance movements, and civilian groups that directly or indirectly engaged in the global conflict between 1939 and 1945.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:51 p.m.