Triple
T19674949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worimi land |
E472428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Aboriginal Country |
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 Aboriginal Country Context triple: [Worimi land, instanceOf, traditional Aboriginal Country]
-
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.
traditional Indigenous Australian language area
A traditional Indigenous Australian language area is a geographically and culturally defined region in which a particular Aboriginal or Torres Strait Islander language (or closely related dialects) is historically spoken and maintained by its associated community.
-
D.
Aboriginal land council
An Aboriginal land council is a representative body established to advocate for, manage, and protect the land rights, cultural heritage, and interests of Aboriginal communities within a defined region.
-
E.
traditional Aboriginal toponym
A traditional Aboriginal toponym is a place name originating from Aboriginal languages and cultural knowledge, often reflecting the land’s features, stories, and spiritual significance.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:45 p.m.