Triple
T26234743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kartinyeri v Commonwealth |
E656132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | High Court of Australia case |
C40477
|
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: High Court of Australia case Context triple: [Kartinyeri v Commonwealth, instanceOf, High Court of Australia case]
-
A.
Supreme Court of India case
A Supreme Court of India case is a legal dispute or matter formally brought before the Supreme Court of India for authoritative interpretation of law, constitutional adjudication, or final appellate review.
-
B.
Aboriginal law case
An Aboriginal law case is a legal dispute or judicial decision that interprets and applies laws, rights, and obligations relating to Indigenous peoples, their lands, cultures, and governance.
-
C.
Canadian court case
A Canadian court case is a formal legal proceeding in which disputes or criminal charges are adjudicated by a court within Canada’s judicial system, resulting in a binding decision based on Canadian law.
-
D.
Aboriginal rights case
chosen
An Aboriginal rights case is a legal proceeding that addresses claims by Indigenous peoples to inherent or treaty-based rights, such as land, resources, self-governance, or cultural practices, and determines how those rights are recognized and protected under state law.
-
E.
Aboriginal title case
An Aboriginal title case is a legal proceeding in which Indigenous peoples seek judicial recognition and protection of their inherent land rights based on traditional occupation and use, rather than on grants from the state.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 9:01 p.m.