Triple

T4737376
Position Surface form Disambiguated ID Type / Status
Subject Siege of Kimberley E105157 entity
Predicate instanceOf P0 FINISHED
Object battle of the Second Boer War C16280 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: battle of the Second Boer War
Context triple: [Siege of Kimberley, instanceOf, battle of the Second Boer War]
  • A. battle of the Second Anglo-Dutch War
    A battle of the Second Anglo-Dutch War is a specific naval or amphibious military engagement fought between English and Dutch forces between 1665 and 1667 as part of their broader conflict over maritime trade and colonial dominance.
  • B. battle of the Second Anglo-Dutch War
    A battle of the Second Anglo-Dutch War is a specific naval or amphibious military engagement fought between English and Dutch forces between 1665 and 1667 as part of their broader conflict for maritime and commercial supremacy.
  • C. 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.
  • D. imperial war
    Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
  • E. event in the Crimean War
    An event in the Crimean War is a specific historical occurrence—such as a battle, diplomatic action, military maneuver, or political decision—that took place between 1853 and 1856 and contributed to the course and outcome of the conflict.
  • 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_69bd43ee52048190b81a4f066534ffb3 completed March 20, 2026, 12:56 p.m.
Created at: March 20, 2026, 1:19 p.m.