Triple

T23687325
Position Surface form Disambiguated ID Type / Status
Subject Reichsstatthalter in Lippe and Schaumburg-Lippe E585204 entity
Predicate instanceOf P0 FINISHED
Object Nazi administrative office C47954 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 office
Context triple: [Reichsstatthalter in Lippe and Schaumburg-Lippe, instanceOf, Nazi administrative office]
  • A. Nazi SS office
    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.
  • B. 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.
  • C. Nazi architecture project
    A Nazi architecture project is a large-scale building or urban planning initiative designed under the Third Reich to embody and propagate Nazi ideology through monumental, authoritarian, and neoclassical forms.
  • D. 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.
  • E. Ottoman government office
    An Ottoman government office is an administrative institution within the Ottoman Empire responsible for managing specific state functions such as taxation, justice, military affairs, or provincial governance under the authority of the sultan and central bureaucracy.
  • F. None of above. chosen

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_69e249037ce0819088b149608e98f685 completed April 17, 2026, 2:51 p.m.
Created at: April 17, 2026, 6:52 p.m.