Triple

T35552567
Position Surface form Disambiguated ID Type / Status
Subject Arakwal Indigenous Land Use Agreement area E1027402 entity
Predicate instanceOf P0 FINISHED
Object Indigenous Land Use Agreement area C47402 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 Land Use Agreement area
Context triple: [Arakwal Indigenous Land Use Agreement area, instanceOf, Indigenous Land Use Agreement area]
  • A. indigenous territory
    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.
  • B. Aboriginal reserve
    An Aboriginal reserve is a tract of land set aside by a government for the use and occupation of Indigenous peoples, typically recognized as a distinct community with certain self-governing rights and cultural protections.
  • C. treaty area chosen
    A treaty area is a geographically defined region whose governance, resource use, or legal status is regulated by one or more formal agreements between sovereign entities or authorities.
  • D. 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.
  • E. 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.
  • 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_69f76e014fd481909e9f04ac603a2aa9 completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:04 p.m.