Triple
T29796486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Tug River |
E756563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the West Virginia Mine Wars |
C56938
|
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 West Virginia Mine Wars Context triple: [Battle of the Tug River, instanceOf, event in the West Virginia Mine Wars]
-
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 King Philip's War
An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred during the 1675–1678 conflict between Native American tribes and English colonists in New England.
-
C.
event in King Philip's War
An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred between 1675 and 1678 during the conflict between Native American tribes and English colonists in New England.
-
D.
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.
-
E.
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.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:15 p.m.