Triple
T21566061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainy Mountain |
E532164
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | site of indigenous significance |
C10087
|
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: site of indigenous significance Context triple: [Rainy Mountain, instanceOf, site of indigenous significance]
-
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.
Haida heritage site
A Haida heritage site is a culturally significant location associated with the Haida Nation, encompassing traditional villages, sacred landscapes, archaeological remains, and places of ongoing cultural practice and identity.
-
C.
Indigenous knowledge initiative
An Indigenous knowledge initiative is a collaborative effort to recognize, preserve, and apply the traditional knowledge, practices, and cultural wisdom of Indigenous communities in ways that support their self-determination and benefit broader society.
-
D.
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.
-
E.
cultural site
chosen
A cultural site is a place of historical, artistic, social, or spiritual significance that embodies and preserves the traditions, values, and heritage of a community or civilization.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:30 p.m.