Triple
T29321662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adat Temenggung |
E743530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Malay customary law |
C54829
|
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: Malay customary law Context triple: [Adat Temenggung, instanceOf, Malay customary law]
-
A.
Malacca Sultanate law code
The Malacca Sultanate law code is a historical legal framework that governed political authority, trade, social conduct, and Islamic practices in the Malacca Sultanate, serving as a foundational reference for later Malay legal traditions.
-
B.
Albanian customary law
Albanian customary law is a traditional, unwritten legal system—most famously embodied in the Kanun—that historically governed social conduct, conflict resolution, and community obligations in Albanian society.
-
C.
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.
-
D.
Sharia court
A Sharia court is a judicial body that interprets and applies Islamic law (Sharia) to resolve disputes and govern personal, family, and sometimes criminal matters among Muslims.
-
E.
Mongol law
Mongol law refers to the legal principles, customary practices, and codified regulations—most notably the Yassa—developed under the Mongol Empire to govern its diverse subjects, maintain military discipline, and ensure social order across vast conquered territories.
- F. None of above. chosen
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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:23 p.m.