Triple
T24946384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coranderrk Aboriginal Station |
E624194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Aboriginal reserve |
C49325
|
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 reserve Context triple: [Coranderrk Aboriginal Station, instanceOf, Aboriginal reserve]
-
A.
First Nations reserve
A First Nations reserve is a tract of land set aside under the Indian Act and treaty agreements for the use and benefit of a specific First Nations community, typically governed by that community’s band council.
-
B.
Indian reserve
An Indian reserve is a tract of land set aside under federal authority for the use and benefit of a specific First Nations community, typically governed by band leadership and subject to distinct legal and administrative frameworks.
-
C.
Indian reservation
An Indian reservation is a tract of land managed by a Native American tribe under the U.S. Bureau of Indian Affairs, where the tribe exercises certain sovereign rights and self-governance.
-
D.
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.
-
E.
indigenous township
An indigenous township is an administrative division or community area primarily inhabited and governed by indigenous peoples, often recognized for preserving their distinct cultural, social, and political practices within a broader national framework.
- F. None of above. chosen
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.