Triple
T4674525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amt I |
E103645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi security administration office |
C2765
|
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 security administration office Context triple: [Amt I, instanceOf, Nazi security administration office]
-
A.
Wehrmacht headquarters
The Wehrmacht headquarters was the central command authority of Nazi Germany's unified armed forces, responsible for strategic planning, coordination, and direction of military operations during World War II.
-
B.
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.
-
C.
Gulag administrative body
The Gulag administrative body is the centralized state organization responsible for planning, managing, and overseeing the operation of forced labor camps within the Soviet penal system.
-
D.
institution of Nazi Germany
chosen
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.
-
E.
Nazi paramilitary unit
A Nazi paramilitary unit is an organized, militarized group aligned with the National Socialist regime that used violence, intimidation, and coercion to enforce its ideology, suppress opposition, and support its political and military objectives.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:15 p.m.