Triple

T37425437
Position Surface form Disambiguated ID Type / Status
Subject Dunmore’s War E929974 entity
Predicate instanceOf P0 FINISHED
Object colonial frontier war C22862 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: colonial frontier war
Context triple: [Dunmore’s War, instanceOf, colonial frontier war]
  • A. Frontier War
    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. 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.
  • C. Anglo–Native American conflict chosen
    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.
  • D. Spanish colonial war
    A Spanish colonial war is an armed conflict involving Spain’s efforts to conquer, control, or defend overseas territories within its colonial empire, typically against indigenous populations, rival European powers, or independence movements.
  • E. frontier militia
    A frontier militia is a locally organized, often semi-formal armed group formed by settlers or border communities to defend remote or contested territories from external threats and maintain basic security.
  • 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_69f76ebf0f288190ba198a78341613b8 completed May 3, 2026, 3:50 p.m.
Created at: May 3, 2026, 4:16 p.m.