Triple
T33842444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madayin |
E867391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yolngu customary law |
C38910
|
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: Yolngu customary law Context triple: [Madayin, instanceOf, Yolngu customary law]
-
A.
Yolngu song tradition
Yolngu song tradition is an Indigenous Australian musical and ceremonial practice in which songs encode ancestral law, land relationships, and clan identity, passed orally through generations as a living archive of Yolngu knowledge and culture.
-
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.
Indigenous legal tradition
chosen
Indigenous legal tradition is a system of law rooted in the customs, values, and governance practices of Indigenous peoples, transmitted through oral histories, ceremonies, and community relationships rather than solely through written statutes.
-
D.
Malay customary law
Malay customary law is the body of traditional norms, practices, and unwritten rules that historically governed social relations, property, and dispute resolution among Malay communities, often coexisting with Islamic law and colonial legal systems.
-
E.
Karbi customary institution
Karbi customary institution refers to the traditional socio-political and judicial structures of the Karbi community that regulate social order, resolve disputes, and preserve cultural norms through customary laws and practices.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.