Triple
T23860237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luhak Limopuluah |
E592426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Minangkabau customary territory |
C48141
|
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: Minangkabau customary territory Context triple: [Luhak Limopuluah, instanceOf, Minangkabau customary territory]
-
A.
Minangkabau royal dynasty
The Minangkabau royal dynasty is the traditional ruling lineage of the Minangkabau people of West Sumatra, Indonesia, historically governing through a matrilineal adat system that blended indigenous customs with Islamic influences.
-
B.
Bugis principality
A Bugis principality is a traditional political entity or small sovereign state historically governed by Bugis rulers in South Sulawesi, Indonesia, characterized by its own leadership, territory, and customary laws.
-
C.
Malay kingdom
A Malay kingdom is a traditional political entity in the Malay world, typically ruled by a sultan or raja, characterized by Malay culture, Islam, and control over regional trade networks.
-
D.
Balinese polity
A Balinese polity is a traditional socio-political entity in Bali characterized by a hierarchical kingship, ritual authority, and complex relationships between royal courts, villages, and religious institutions.
-
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. 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:12 p.m.