Triple

T11832881
Position Surface form Disambiguated ID Type / Status
Subject Occupied Enemy Territory East E281437 entity
Predicate instanceOf P0 FINISHED
Object World War I military occupation C833 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: World War I military occupation
Context triple: [Occupied Enemy Territory East, instanceOf, World War I military occupation]
  • A. military occupation chosen
    A military occupation is the effective control and administration of a territory by foreign armed forces without the sovereign consent of the territory’s recognized government.
  • B. World War I military formation
    A World War I military formation is an organized grouping of soldiers, equipment, and command structures arranged for combat operations according to the tactical doctrines and technological constraints of the 1914–1918 conflict.
  • C. World War I military operation
    A World War I military operation is a coordinated set of strategic and tactical actions conducted by armed forces during the First World War to achieve specific military objectives within a defined time and geographic area.
  • D. World War I-era polity
    A World War I-era polity is a sovereign or semi-sovereign political entity that existed and exercised governmental authority during the period surrounding the First World War (circa 1914–1918), shaped by the war’s diplomatic, military, and social upheavals.
  • E. World War I site
    A World War I site is a historically significant location directly associated with events, operations, or impacts of the First World War, such as battlefields, trenches, memorials, cemeteries, or military installations.
  • 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_69d6ab276f8c8190b1966a0ef11349ac completed April 8, 2026, 7:23 p.m.
Created at: April 8, 2026, 9:43 p.m.