Triple
T33931718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagaruyung dynasty |
E869914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Minangkabau royal house |
C27448
|
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 royal house Context triple: [Pagaruyung dynasty, instanceOf, Minangkabau royal house]
-
A.
Minangkabau royal dynasty
chosen
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.
Makassarese kingdom
The Makassarese kingdom was a historical maritime polity centered in South Sulawesi, Indonesia, known for its powerful trading ports, Islamic influence, and resistance to European colonial expansion in the early modern period.
-
C.
Javanese monarchy
A Javanese monarchy is a traditional hierarchical system of kingship in Java that blends indigenous customs, Islamic influences, and courtly culture to legitimize political authority and spiritual power.
-
D.
Minangkabau customary territory
Minangkabau customary territory is the traditional socio-cultural and ancestral land domain of the Minangkabau people, defined by their matrilineal adat (customary law), communal land rights, and shared cultural identity rather than formal administrative boundaries.
-
E.
Malay royal dynasty
A Malay royal dynasty is a hereditary ruling family of Malay origin that traditionally governs a Malay state or sultanate, embodying political authority, cultural leadership, and continuity of lineage.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.