Triple
T8811886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luther Memorandum |
E209683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi document |
C13546
|
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 document Context triple: [Luther Memorandum, instanceOf, Nazi document]
-
A.
Nazi report
chosen
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.
-
B.
World War II document
A World War II document is an original or reproduced written, printed, or recorded artifact created during or directly concerning the events, policies, operations, or experiences of the Second World War.
-
C.
Nazi official
A Nazi official is a person who held an administrative, political, or military position within the National Socialist (Nazi) regime in Germany, responsible for implementing and enforcing its totalitarian, racist, and genocidal policies.
-
D.
Soviet document
A Soviet document is an official or unofficial written record produced within the Soviet Union’s political, administrative, or social systems, reflecting its bureaucratic procedures, ideology, and historical context.
-
E.
institution of Nazi Germany
An institution of Nazi Germany is any formal organization, governmental body, or structured system established or co-opted by the Nazi regime to implement, enforce, or propagate its totalitarian, racist, and expansionist policies between 1933 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:45 p.m.