Triple
T36309737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Reinhard headquarters in Lublin |
E894035
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi administrative headquarters |
C23961
|
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 administrative headquarters Context triple: [Operation Reinhard headquarters in Lublin, instanceOf, Nazi administrative headquarters]
-
A.
Nazi administrative office
A Nazi administrative office was a bureaucratic unit within the Third Reich responsible for implementing, coordinating, and managing policies and operations in line with National Socialist ideology and state objectives.
-
B.
Führer Headquarters
The Führer Headquarters were a series of heavily fortified command complexes used by Adolf Hitler and the Nazi leadership during World War II to plan and direct military operations.
-
C.
Nazi SS office
chosen
A Nazi SS office was an administrative and operational unit of the Schutzstaffel responsible for planning, coordinating, and executing the regime’s ideological, security, and genocidal policies.
-
D.
Nazi military installation
A Nazi military installation is a facility established and operated by the German armed forces under the Nazi regime for purposes such as training, command, logistics, weapons development, or the launching and support of military operations.
-
E.
Nazi Party rally site
A Nazi Party rally site is a large, purpose-built or adapted location used by the National Socialist German Workers' Party for mass gatherings, propaganda events, and demonstrations of political power in Germany between 1920 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.