Triple
T16998036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Vishnuvardhana |
E412367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Singhasari |
C14597
|
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: ruler of Singhasari Context triple: [Sri Vishnuvardhana, instanceOf, ruler of Singhasari]
-
A.
Javanese king
chosen
A Javanese king is the supreme traditional ruler of a Javanese kingdom, embodying both political authority and spiritual legitimacy within Javanese culture and cosmology.
-
B.
Javanese dynasty
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.
-
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.
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.
-
E.
Majapahit nobility
Majapahit nobility were the elite ruling class of the Majapahit Empire in Java, comprising royal family members, high-ranking officials, and regional lords who held political, military, and administrative power.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.