Triple
T28831415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Tellico (1798) |
E728060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cherokee–United States treaty |
C566
|
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: Cherokee–United States treaty Context triple: [Treaty of Tellico (1798), instanceOf, Cherokee–United States treaty]
-
A.
Cherokee
Cherokee: A Native American people originally from the southeastern United States, known for their rich cultural traditions, complex social and political structures, and resilience through forced removal and adaptation.
-
B.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
Haudenosaunee territory
Haudenosaunee territory refers to the traditional and contemporary lands inhabited, used, and governed by the Haudenosaunee Confederacy, spanning parts of what is now New York State, Ontario, and Quebec.
-
D.
Kickapoo tribe
The Kickapoo tribe is a Native American people originally from the Great Lakes region, known for their resistance to displacement, semi-nomadic lifestyle, and communities now located in Oklahoma, Kansas, Texas, and Mexico.
-
E.
Mapuche–Spanish diplomatic agreement
A Mapuche–Spanish diplomatic agreement is a formal treaty or negotiated settlement between Mapuche authorities and representatives of the Spanish Crown that defined mutual obligations, territorial boundaries, and mechanisms for coexistence or conflict resolution.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:37 a.m.