Triple

T9783882
Position Surface form Disambiguated ID Type / Status
Subject Mimbres Apache conflicts E237443 entity
Predicate instanceOf P0 FINISHED
Object Apache Wars engagement C26252 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: Apache Wars engagement
Context triple: [Mimbres Apache conflicts, instanceOf, Apache Wars engagement]
  • A. engagement of the Nine Years' War
    An engagement of the Nine Years' War is a specific military confrontation—such as a battle, siege, raid, or skirmish—fought between the war’s opposing coalitions within the broader 1688–1697 conflict.
  • B. Anglo-Scottish war
    The Anglo-Scottish War refers to the series of intermittent military conflicts and political struggles between the kingdoms of England and Scotland, primarily from the late 13th to early 17th centuries, over sovereignty, territory, and dynastic claims.
  • C. battle of the Nine Years' War
    A battle of the Nine Years' War is a military engagement fought between 1688 and 1697 involving the Grand Alliance and France, characterized by early modern tactics, shifting coalitions, and the broader struggle for European balance of power.
  • D. engagement of the Hundred Years' War
    An engagement of the Hundred Years' War is a specific military confrontation—ranging from major battles to minor skirmishes—fought between English and French (and their allies') forces within the broader conflict spanning 1337 to 1453.
  • E. campaign of the Nine Years' War
    A campaign of the Nine Years' War is a coordinated series of military operations conducted by one or more belligerents within a specific theater and timeframe between 1688 and 1697, aimed at achieving strategic objectives in the broader 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_69ca84da927881909bda80caecad6010 completed March 30, 2026, 2:12 p.m.
Created at: March 30, 2026, 8:27 p.m.