Triple
T28103632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attikamek |
E710302
|
entity |
| Predicate | traditionalTerritoryName |
P28559
|
FINISHED |
| Object | Nitaskinan |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Nitaskinan | Statement: [Attikamek, traditionalTerritoryName, Nitaskinan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalTerritoryName Context triple: [Attikamek, traditionalTerritoryName, Nitaskinan]
-
A.
traditionalTerritorialDesignation
Indicates a historically or culturally recognized claim or assignment of a geographic area to a particular group, authority, or identity.
-
B.
indigenousNameOf
Indicates that one entity is the name used for another entity in an indigenous or native language.
-
C.
indigenousTerritoryOf
chosen
Indicates that a geographic area is traditionally inhabited, used, or claimed by a particular Indigenous people or community as their ancestral territory.
-
D.
alternativeNameOfTerritory
Indicates that one territory is known or referred to by an alternative name corresponding to another territory.
-
E.
traditionalTerritoryUse
Indicates that an entity uses or occupies a territory in ways that follow long-established, customary, or ancestral practices.
- F. None of above.
Provenance (3 batches)
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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 27, 2026, 9:06 p.m.