Triple
T31510066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mi'kmaq–British treaties |
E803917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century treaties |
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: 18th-century treaties Context triple: [Mi'kmaq–British treaties, instanceOf, 18th-century treaties]
-
A.
modern treaty
A modern treaty is a contemporary, negotiated agreement between Indigenous peoples and a state that defines rights, land ownership, governance, and resource management in a legally binding framework.
-
B.
treaty system
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
-
C.
early 18th-century conflict
An early 18th-century conflict is a historically situated armed struggle or war occurring roughly between 1700 and 1750, shaped by emerging nation-states, dynastic rivalries, and evolving military technologies and tactics.
-
D.
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.
-
E.
18th-century organization
An 18th-century organization is a formally or informally structured group of individuals operating during the 1700s to pursue political, economic, social, religious, or intellectual objectives within the historical context of early modern society.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:49 p.m.