Triple

T23369561
Position Surface form Disambiguated ID Type / Status
Subject Red Cloud E593423 entity
Predicate militaryConflict P12 FINISHED
Object Bozeman War NE NERFINISHED

How this triple was built (3 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Bozeman War | Statement: [Red Cloud, militaryConflict, Bozeman War]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bozeman War
Context triple: [Red Cloud, militaryConflict, Bozeman War]
  • A. Nez Perce War
    The Nez Perce War was an 1877 conflict in which the U.S. Army pursued the Nez Perce tribe across the Pacific Northwest as they attempted a strategic retreat toward Canada rather than submit to forced relocation.
  • B. Aroostook War
    The Aroostook War was a bloodless 19th-century border dispute between the United States and British North America over the Maine–New Brunswick boundary that was ultimately resolved through diplomacy.
  • C. Winnebago War
    The Winnebago War was a brief 1827 conflict between the United States and the Ho-Chunk (Winnebago) people in the Upper Mississippi region, sparked by tensions over land cessions and American expansion.
  • D. Bannock War
    The Bannock War was an 1878 armed conflict in the American West between the Bannock people and the United States, sparked by tensions over broken treaties, land encroachment, and dwindling food resources.
  • E. Goshute War
    The Goshute War was a mid-19th-century conflict in the American West between the Goshute people and the United States, largely sparked by tensions over mail routes, resource use, and encroaching settlement on Goshute lands.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Bozeman War
Target entity description: The Bozeman War was a mid-1860s conflict between the United States and several Lakota-led Native American groups over control of the Bozeman Trail and hunting grounds in the northern Great Plains.
  • A. Nez Perce War
    The Nez Perce War was an 1877 conflict in which the U.S. Army pursued the Nez Perce tribe across the Pacific Northwest as they attempted a strategic retreat toward Canada rather than submit to forced relocation.
  • B. Aroostook War
    The Aroostook War was a bloodless 19th-century border dispute between the United States and British North America over the Maine–New Brunswick boundary that was ultimately resolved through diplomacy.
  • C. Winnebago War
    The Winnebago War was a brief 1827 conflict between the United States and the Ho-Chunk (Winnebago) people in the Upper Mississippi region, sparked by tensions over land cessions and American expansion.
  • D. Bannock War
    The Bannock War was an 1878 armed conflict in the American West between the Bannock people and the United States, sparked by tensions over broken treaties, land encroachment, and dwindling food resources.
  • E. Goshute War
    The Goshute War was a mid-19th-century conflict in the American West between the Goshute people and the United States, largely sparked by tensions over mail routes, resource use, and encroaching settlement on Goshute lands.
  • F. None of above. chosen

Provenance (2 batches)

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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0aff84c8190a5a6bf52adae1c9a completed April 29, 2026, 6:09 a.m.
Created at: April 17, 2026, 5:32 p.m.