Triple
T27357152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of 1646 |
E685714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Indigenous 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: Anglo-Indigenous treaty Context triple: [Treaty of 1646, instanceOf, Anglo-Indigenous treaty]
-
A.
Indian Act
The Indian Act is a Canadian federal law that governs the status, rights, and administration of First Nations peoples and communities, historically enabling extensive government control and assimilation policies.
-
B.
Aboriginal Australian alliance
An Aboriginal Australian alliance is a cooperative relationship or coalition formed between different Aboriginal Australian groups, communities, or organizations to pursue shared cultural, political, social, or land-related goals.
-
C.
Aboriginal rights case
An Aboriginal rights case is a legal proceeding that addresses claims by Indigenous peoples to inherent or treaty-based rights, such as land, resources, self-governance, or cultural practices, and determines how those rights are recognized and protected under state law.
-
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.
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.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:51 a.m.