Triple

T34326000
Position Surface form Disambiguated ID Type / Status
Subject Tasmanian frontier conflict E880866 entity
Predicate instanceOf P0 FINISHED
Object Australian frontier conflict C30449 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: Australian frontier conflict
Context triple: [Tasmanian frontier conflict, instanceOf, Australian frontier conflict]
  • A. Frontier War chosen
    Frontier War is a prolonged, often low-intensity conflict that occurs along or beyond a political or cultural boundary, characterized by skirmishes, raids, and contested control of sparsely governed territories.
  • B. Anglo–Native American conflict
    Anglo–Native American conflict refers to the prolonged series of violent and nonviolent confrontations, negotiations, and power struggles between English (and later Anglo-American) settlers and Indigenous peoples in North America over land, resources, sovereignty, and cultural survival.
  • C. Xhosa Wars
    The Xhosa Wars were a series of nine frontier conflicts between the Xhosa peoples and European colonists in the Eastern Cape of South Africa from the late 18th to late 19th centuries, driven by competition over land, cattle, and political control.
  • D. Old West conflict
    A tense and often violent confrontation set in the American frontier era, typically involving cowboys, outlaws, lawmen, and settlers clashing over land, justice, or survival.
  • E. Native American war
    A Native American war is an armed conflict involving Indigenous peoples of the Americas, often fought to defend their lands, resources, sovereignty, and cultural survival against other Native groups or external powers.
  • 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_69f349b9cd508190a996a616903b3e6d completed April 30, 2026, 12:23 p.m.
Created at: May 1, 2026, 1:58 a.m.