Triple
T1810383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creek War of 1836 |
E40317
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Native American–United States conflict |
C3287
|
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: Native American–United States conflict Context triple: [Creek War of 1836, instanceOf, Native American–United States conflict]
-
A.
Indian reservation
An Indian reservation is a tract of land managed by a Native American tribe under the U.S. Bureau of Indian Affairs, where the tribe exercises certain sovereign rights and self-governance.
-
B.
Native American weapon
A Native American weapon is a tool or implement traditionally crafted and used by Indigenous peoples of the Americas for hunting, warfare, or ceremonial purposes, often reflecting the materials, environment, and cultural practices of specific tribes.
-
C.
guerrilla conflict
chosen
Guerrilla conflict is a form of irregular warfare in which small, mobile groups use hit-and-run tactics, ambushes, and sabotage to challenge a larger, conventionally organized force, often relying on local support and intimate knowledge of the terrain.
-
D.
19th-century conflict
A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
-
E.
Mesoamerican alliance
A Mesoamerican alliance is a political and military coalition formed between pre-Columbian Mesoamerican city-states or polities to coordinate warfare, trade, tribute, and regional dominance.
- 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.