Triple
T18581345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zugubal cosmology |
E454121
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancestral law system |
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: ancestral law system Context triple: [Zugubal cosmology, instanceOf, ancestral law system]
-
A.
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.
-
B.
colonial legal system
A colonial legal system is a framework of laws, courts, and enforcement mechanisms imposed by a colonizing power to govern a colonized territory, typically prioritizing imperial interests and often subordinating or reshaping indigenous legal traditions.
-
C.
civil law tradition
The civil law tradition is a legal system rooted in comprehensive written codes and statutes, derived primarily from Roman law, in which judges apply and interpret codified rules rather than relying heavily on judicial precedent.
-
D.
system of laws
A system of laws is an organized and coherent set of rules and principles established by an authority to regulate behavior, resolve disputes, and maintain order within a society.
-
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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.