Triple
T16065065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qin–Xiongnu conflicts |
E389710
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | frontier war |
C30449
|
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: frontier war Context triple: [Qin–Xiongnu conflicts, instanceOf, frontier war]
-
A.
Frontier War
chosen
Frontier War is a prolonged, often low-intensity conflict that occurs along or beyond a political or cultural boundary, characterized by skirmishes, raids, and contested control of sparsely governed territories.
-
B.
Native American war
A Native American war is an armed conflict involving Indigenous peoples of the Americas, often fought to defend their lands, resources, sovereignty, and cultural survival against other Native groups or external powers.
-
C.
Old West conflict
A tense and often violent confrontation set in the American frontier era, typically involving cowboys, outlaws, lawmen, and settlers clashing over land, justice, or survival.
-
D.
Anglo–Native American conflict
Anglo–Native American conflict refers to the prolonged series of violent and nonviolent confrontations, negotiations, and power struggles between English (and later Anglo-American) settlers and Indigenous peoples in North America over land, resources, sovereignty, and cultural survival.
-
E.
battle of the Northwest Indian War
A battle of the Northwest Indian War is an armed military engagement between United States forces and a coalition of Native American nations fought in the Old Northwest between 1785 and 1795 as part of the struggle for control of the region.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:57 a.m.