Triple
T22636368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millowl |
E558690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous place name |
C21680
|
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: Indigenous place name Context triple: [Millowl, instanceOf, Indigenous place name]
-
A.
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.
-
B.
Native American place name
A Native American place name is a geographic name derived from the languages and naming traditions of Indigenous peoples of the Americas, often reflecting local features, history, or cultural significance.
-
C.
Indigenous Australian place name
chosen
An Indigenous Australian place name is a toponym originating from the languages and cultural traditions of Aboriginal and Torres Strait Islander peoples, often reflecting features of the land, water, sky, or ancestral stories connected to that location.
-
D.
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.
-
E.
historical place name
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:03 p.m.