Triple

T3241821
Position Surface form Disambiguated ID Type / Status
Subject Siege of Louisbourg (1745) E67980 entity
Predicate instanceOf P0 FINISHED
Object event in North American colonial history C383 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: event in North American colonial history
Context triple: [Siege of Louisbourg (1745), instanceOf, event in North American colonial history]
  • A. colonial-era event chosen
    A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
  • B. event in King Philip's War
    An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred during the 1675–1678 conflict between Native American tribes and English colonists in New England.
  • C. event in King Philip's War
    An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred between 1675 and 1678 during the conflict between Native American tribes and English colonists in New England.
  • D. Revolutionary War institution
    A Revolutionary War institution is an organized body, such as a military, governmental, or civic entity, established or transformed during the American Revolution to support, administer, or legitimize the war effort and emerging nation.
  • E. Revolutionary War institution
    A Revolutionary War institution is an organized body—such as a military unit, governing council, or support organization—established during the American Revolution to coordinate, supply, or direct the war effort and emerging governance.
  • 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_69ad858d27348190abb61c280b4c86a9 completed March 8, 2026, 2:19 p.m.
Created at: March 8, 2026, 3:08 p.m.