Triple
T34721193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stillman’s Run battlefield |
E1000918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Black Hawk War site |
C61961
|
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: Black Hawk War site Context triple: [Stillman’s Run battlefield, instanceOf, Black Hawk War site]
-
A.
War of 1812 site
A War of 1812 site is a historically significant location directly associated with military, political, or civilian events of the War of 1812, such as battlefields, forts, encampments, or related structures and landscapes.
-
B.
Second Seminole War site
A Second Seminole War site is a historically significant location associated with battles, encampments, negotiations, or other key events that occurred during the Second Seminole War (1835–1842) in Florida.
-
C.
French and Indian War site
A French and Indian War site is a location significantly associated with military, political, or cultural events of the French and Indian War (1754–1763), such as battlefields, forts, encampments, or related historic landscapes.
-
D.
Sauk settlement
A Sauk settlement is a community or village established and inhabited by the Sauk (Sac) people, typically organized around kinship networks, seasonal subsistence activities, and cultural practices in their traditional homelands.
-
E.
King Philip’s War site
A King Philip’s War site is a historically significant location directly associated with the events, battles, encampments, or aftermath of the 1675–1678 conflict between New England colonists and Indigenous peoples.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.