Triple

T16319791
Position Surface form Disambiguated ID Type / Status
Subject Illinois campaign E396260 entity
Predicate instanceOf P0 FINISHED
Object Revolutionary War campaign C14349 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: Revolutionary War campaign
Context triple: [Illinois campaign, instanceOf, Revolutionary War campaign]
  • A. American Revolutionary War engagement
    An American Revolutionary War engagement is a specific military encounter or battle between opposing forces during the American Revolution, typically involving organized combat over strategic objectives.
  • B. Revolutionary War event chosen
    A Revolutionary War event is a significant occurrence—such as a battle, political decision, treaty, or social upheaval—that directly influenced the course, conduct, or outcome of the American Revolutionary War.
  • C. 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.
  • D. 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.
  • E. Revolutionary War site
    A Revolutionary War site is a historically significant location where events, battles, encampments, or strategic activities related to the American Revolutionary War took place and are preserved or interpreted today.
  • 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_69d87f255b788190a400eba031dd85d8 completed April 10, 2026, 4:40 a.m.
Created at: April 10, 2026, 5:06 a.m.