Triple

T33081989
Position Surface form Disambiguated ID Type / Status
Subject Gaspee Affair E846531 entity
Predicate instanceOf P0 FINISHED
Object pre-Revolutionary incident C52333 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: pre-Revolutionary incident
Context triple: [Gaspee Affair, instanceOf, pre-Revolutionary incident]
  • A. pre-Revolutionary conflict chosen
    A pre-Revolutionary conflict is a period of escalating political, social, and economic tensions, often marked by protests, ideological disputes, and sporadic violence, that precedes and contributes to the outbreak of a full-scale revolution.
  • B. antebellum United States incident
    An antebellum United States incident is a discrete event or occurrence that took place in the U.S. between the late 18th century and the outbreak of the Civil War in 1861, often reflecting the era’s social, political, or sectional tensions.
  • C. anti-Chinese incident
    An anti-Chinese incident is an event or action, ranging from verbal harassment to physical violence or discriminatory policies, specifically targeting individuals, communities, or institutions perceived as Chinese.
  • D. Calvinist uprising
    A Calvinist uprising is a rebellion or series of revolts driven by communities or leaders inspired by Calvinist Protestant beliefs, typically challenging established religious or political authorities to impose or defend Reformed doctrines and practices.
  • E. revolutionary revolt
    A revolutionary revolt is a collective, often radical uprising aimed at overthrowing an existing political or social order to establish a fundamentally new system.
  • 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_69f34954d46c8190a04a159cc5f99efd completed April 30, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:26 a.m.