Triple
T16857724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panangkaran |
E409828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sailendra dynasty ruler |
C14974
|
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: Sailendra dynasty ruler Context triple: [Panangkaran, instanceOf, Sailendra dynasty ruler]
-
A.
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.
-
B.
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.
-
C.
Buddhist ruler
A Buddhist ruler is a sovereign who governs according to Buddhist principles, promoting compassion, non-violence, moral conduct, and the welfare of all beings within their realm.
-
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.
Javanese dynasty
chosen
A Javanese dynasty is a ruling lineage or royal house originating from the island of Java, Indonesia, that holds political, cultural, and spiritual authority over a Javanese kingdom or realm across generations.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:24 a.m.