Triple
T32311382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of 1805 |
E825508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States–Dakota 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: United States–Dakota treaty Context triple: [Treaty of 1805, instanceOf, United States–Dakota treaty]
-
A.
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.
-
B.
Dakota tribe
The Dakota tribe is a Native American people of the Sioux Nation traditionally inhabiting the northern Great Plains and woodlands, known for their rich oral traditions, kinship-based social structure, and deep spiritual connection to the land.
-
C.
Miniconjou Lakota
Miniconjou Lakota are a division of the Lakota Sioux people historically residing in the central Great Plains, known for their distinct bands, cultural traditions, and role in 19th-century Plains history.
-
D.
institution of the Northwest Territory
An institution of the Northwest Territory is an organized governmental, legal, educational, or social body established to administer, regulate, or support public life within the historical Northwest Territory of the United States.
-
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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:46 a.m.