Triple
T23764783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cree traditional lands |
E587347
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous ancestral land |
C9388
|
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: Indigenous ancestral land Context triple: [Cree traditional lands, instanceOf, Indigenous ancestral land]
-
A.
indigenous territory
An indigenous territory is a geographically defined area traditionally inhabited, used, or managed by an Indigenous people, where they maintain cultural, spiritual, social, and often legal relationships to the land and its resources.
-
B.
ancestral homeland
chosen
An ancestral homeland is a geographic region to which a person or group traces deep historical, cultural, or familial origins, often forming a core part of their collective identity.
-
C.
Indigenous land rights document
A formal record that asserts, defines, or protects the legal and customary rights of Indigenous peoples to their traditional lands, territories, and resources.
-
D.
Indigenous dwelling
An Indigenous dwelling is a traditional, culturally specific structure designed and built by Indigenous peoples using locally available materials to provide shelter, support community life, and embody spiritual and environmental relationships.
-
E.
Aboriginal place name
An Aboriginal place name is a geographic name derived from the languages and cultural traditions of Indigenous Australian peoples, often reflecting features of the land, water, flora, fauna, or ancestral stories associated with that location.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:15 p.m.