Triple
T17652692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butchulla Aboriginal Corporation |
E429533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | registered native title body corporate |
C36014
|
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: registered native title body corporate Context triple: [Butchulla Aboriginal Corporation, instanceOf, registered native title body corporate]
-
A.
native title body corporate
chosen
A native title body corporate is an Indigenous-owned legal entity established to hold, manage, and protect native title rights and interests on behalf of a native title group after a determination is made.
-
B.
nationalized body
A nationalized body is an organization or enterprise that has been taken into public ownership and control by a national government, typically to manage services or industries deemed of strategic or public interest.
-
C.
corporate board
A corporate board is a group of individuals elected by shareholders to oversee a company's management, set strategic direction, and ensure accountability and compliance with laws and regulations.
-
D.
Alaska Native regional corporation
An Alaska Native regional corporation is a for-profit entity established under the Alaska Native Claims Settlement Act to manage land, financial assets, and business interests on behalf of Alaska Native shareholders within a specific geographic region.
-
E.
public-law corporation
A public-law corporation is a legal entity created by a government statute to perform specific public functions or services, operating with a degree of autonomy but subject to public law and governmental oversight.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 6:05 a.m.