Triple

T13821248
Position Surface form Disambiguated ID Type / Status
Subject Jüdischer Ordnungsdienst E332138 entity
Predicate instanceOf P0 FINISHED
Object Organisation im Zweiten Weltkrieg C34233 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: Organisation im Zweiten Weltkrieg
Context triple: [Jüdischer Ordnungsdienst, instanceOf, Organisation im Zweiten Weltkrieg]
  • A. Wehrmacht high command
    The Wehrmacht high command was the central military leadership of Nazi Germany responsible for planning, directing, and coordinating the operations of the German armed forces during the Second World War.
  • B. Wehrmacht organization
    The Wehrmacht organization is a structured representation of the hierarchical, functional, and administrative components of Nazi Germany’s unified armed forces, including their command chains, unit types, and operational relationships.
  • C. ас Второй мировой войны
    Ас Второй мировой войны — это высококвалифицированный военный лётчик, одержавший значительное количество подтверждённых воздушных побед в ходе боевых действий Второй мировой войны.
  • D. batalla de la Segunda Guerra Mundial
    Una batalla de la Segunda Guerra Mundial es un enfrentamiento militar específico, terrestre, naval o aéreo, ocurrido entre 1939 y 1945, que involucró fuerzas de las potencias aliadas y/o del Eje con objetivos estratégicos definidos dentro del conflicto global.
  • E. World War II home front workforce
    The World War II home front workforce comprises the civilian men and women who filled industrial, agricultural, and support roles to sustain military production and national economies while many traditional workers served in the armed forces.
  • 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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
Created at: April 9, 2026, 10:12 p.m.