Triple
T31975234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngunnawal traditional lands |
E816433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional lands |
C21045
|
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: traditional lands Context triple: [Ngunnawal traditional lands, instanceOf, traditional lands]
-
A.
traditional homeland
A traditional homeland is a geographic area historically inhabited, used, and culturally identified with by an Indigenous or long-established community, forming the core of its ancestral identity and way of life.
-
B.
indigenous territory
chosen
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.
-
C.
public reserved land
Public reserved land is a designated area owned or controlled by a government entity and legally set aside for specific public purposes such as conservation, recreation, infrastructure, or future community use, restricting private development and exploitation.
-
D.
traditional area
A traditional area is a geographically defined region recognized for its longstanding cultural, historical, or customary significance, often governed by inherited practices and community norms.
-
E.
indigenous cultural landscape
An indigenous cultural landscape is a geographic area shaped by the long-term, reciprocal relationships between Indigenous peoples and their environment, reflecting their cultural practices, knowledge systems, and spiritual values.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:11 a.m.