Triple
T15874856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aktion 1005 |
E384927
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi operation |
C29310
|
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: Nazi operation Context triple: [Aktion 1005, instanceOf, Nazi operation]
-
A.
Nazi military operation
A Nazi military operation is a planned and coordinated action conducted by the armed forces of Nazi Germany to achieve specific strategic, tactical, or political objectives during its period of rule, particularly in World War II.
-
B.
Holocaust deportation operation
chosen
A Holocaust deportation operation is a coordinated, state-organized process by which Nazi authorities and collaborators identified, rounded up, and forcibly transported Jews and other targeted groups from their homes or ghettos to concentration, labor, or extermination camps as part of the genocidal policies of the Third Reich.
-
C.
Kriegsmarine operation
A Kriegsmarine operation is a coordinated naval action planned and executed by Nazi Germany’s navy during World War II to achieve specific military, strategic, or logistical objectives at sea.
-
D.
Nazi report
A Nazi report is an official document produced by Nazi authorities or affiliated organizations that records observations, decisions, policies, or activities in line with the regime’s ideological, political, or military objectives.
-
E.
Nazi death marches
Nazi death marches were forced evacuations of concentration camp prisoners on brutal, often lethal marches near the end of World War II, intended to prevent their liberation and conceal evidence of Nazi atrocities.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.