Triple
T33901889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ungud |
E869067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Aboriginal deity |
C28151
|
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: Australian Aboriginal deity Context triple: [Ungud, instanceOf, Australian Aboriginal deity]
-
A.
Aboriginal Australian religious concept
chosen
An Aboriginal Australian religious concept is a culturally specific belief, practice, or spiritual principle rooted in Indigenous Australian cosmologies, ancestral beings, and relationships to land, law, and community.
-
B.
Aboriginal Australian
An Aboriginal Australian is a member of the Indigenous peoples of the Australian continent, belonging to diverse cultural and linguistic groups with deep ancestral connections to the land and rich traditions spanning tens of thousands of years.
-
C.
Aboriginal Australian ancestor
An Aboriginal Australian ancestor is a revered forebear whose spiritual presence, stories, and actions in the Dreaming shape the land, laws, kinship, and cultural identity of their descendants.
-
D.
Kaurna cultural tradition
Kaurna cultural tradition encompasses the customs, stories, language, spiritual beliefs, and practices of the Kaurna people of the Adelaide Plains, expressing their deep connection to Country and community across generations.
-
E.
Aboriginal cultural concept
An Aboriginal cultural concept is a foundational idea, practice, or belief rooted in the traditions, knowledge systems, and worldviews of Aboriginal peoples, often expressing their relationships to land, community, spirituality, and identity.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.