Triple

T30993228
Position Surface form Disambiguated ID Type / Status
Subject siege of the TA Ranch E789721 entity
Predicate instanceOf P0 FINISHED
Object event in the Johnson County War C58979 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 the Johnson County War
Context triple: [siege of the TA Ranch, instanceOf, event in the Johnson County War]
  • A. event in Bleeding Kansas
    An event in Bleeding Kansas is a specific historical incident of political conflict or violent confrontation between pro-slavery and anti-slavery forces in the Kansas Territory during the mid-1850s.
  • B. event in the Black Hawk War
    An event in the Black Hawk War is a specific historical occurrence—such as a battle, treaty, movement, or decision—directly related to the 1832 conflict between Black Hawk’s band and United States forces.
  • C. event in the Great Sioux War of 1876
    An event in the Great Sioux War of 1876 is a specific historical occurrence—such as a battle, treaty negotiation, military campaign, or related incident—that took place during the conflict between the United States and the Lakota Sioux and their allies in 1876.
  • D. event in the Creek War
    An event in the Creek War is a specific historical occurrence—such as a battle, treaty, or raid—taking place during the 1813–1814 conflict between the Creek Nation, the United States, and allied Native groups.
  • E. event in the Apache Wars
    An "event in the Apache Wars" is a specific historical incident, such as a battle, raid, treaty, or negotiation, that occurred during the series of armed conflicts between various Apache groups and the United States (and earlier Mexican) authorities in the 19th century.
  • 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_69f224c65a348190baaed1c01a29900c completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 8:56 p.m.