Triple
T17565533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rakai Pikatan Dyah Saladu |
E427802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sanjaya dynasty ruler |
C38033
|
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: Sanjaya dynasty ruler Context triple: [Rakai Pikatan Dyah Saladu, instanceOf, Sanjaya dynasty ruler]
-
A.
Talpur dynasty ruler
A Talpur dynasty ruler is a sovereign from the Baluch Talpur clan who governed parts of Sindh in the late 18th and early 19th centuries, overseeing regional administration, military affairs, and cultural patronage until British annexation.
-
B.
Manghit dynasty ruler
A Manghit dynasty ruler is a sovereign from the Uzbek Manghit family who governed the Emirate of Bukhara, overseeing its political, military, and religious affairs from the mid-18th to early 20th centuries.
-
C.
Sailendra dynasty member
A Sailendra dynasty member is an individual belonging to the influential Buddhist ruling family that dominated parts of Java and Sumatra in Southeast Asia between the 8th and 9th centuries, known for monumental architecture like Borobudur and extensive maritime trade.
-
D.
Hindu ruler
A Hindu ruler is a sovereign or monarch who governs a territory while adhering to, promoting, or being culturally shaped by Hindu religious, social, and philosophical traditions.
-
E.
pre-Mataram ruler
chosen
A pre-Mataram ruler is a monarch or chieftain who governed territories in the Indonesian archipelago before the rise of the Mataram Kingdom, shaping early political and cultural developments in the region.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.