Triple

T167560
Position Surface form Disambiguated ID Type / Status
Subject Siege of Boston E3049 entity
Predicate instanceOf P0 FINISHED
Object battle of the American Revolutionary War C647 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: battle of the American Revolutionary War
Context triple: [Siege of Boston, instanceOf, battle of the American Revolutionary War]
  • A. event in the War of 1812
    An "event in the War of 1812" is a specific historical occurrence—such as a battle, treaty, political decision, or military campaign—that took place between 1812 and 1815 and directly relates to the conflict between the United States, the United Kingdom, and their respective allies.
  • B. battles chosen
    Battles are organized, often large-scale armed conflicts between opposing forces, characterized by strategic maneuvers, tactical engagements, and the pursuit of specific military objectives within a defined time and place.
  • C. colonial-era event
    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.
  • D. 19th-century conflict
    A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
  • E. phase of World War II
    A phase of World War II is a distinct, time-bounded period of the conflict characterized by specific strategic objectives, major campaigns, and shifts in military, political, or economic conditions.
  • 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_69a2524ce1e48190ab066bf72859f474 completed Feb. 28, 2026, 2:26 a.m.
Created at: Feb. 28, 2026, 2:34 a.m.