Triple
T24945753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aboriginal heritage of Melbourne |
E624181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Aboriginal heritage |
C4934
|
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: Aboriginal heritage Context triple: [Aboriginal heritage of Melbourne, instanceOf, Aboriginal heritage]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Aboriginal-owned organisation
An Aboriginal-owned organisation is an entity that is majority-owned, controlled, and governed by Aboriginal people, operating to advance their cultural, social, and economic interests.
-
E.
cultural heritage
chosen
Cultural heritage is the collective legacy of tangible artifacts and intangible attributes—such as traditions, languages, arts, and historical sites—passed down through generations that shape a community’s identity and 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 5:54 a.m.