Triple
T14444014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Rajasa |
E358157
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Javanese royal dynasty |
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: Javanese royal dynasty Context triple: [House of Rajasa, instanceOf, Javanese royal dynasty]
-
A.
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.
-
B.
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.
-
C.
Javanese king
A Javanese king is the supreme traditional ruler of a Javanese kingdom, embodying both political authority and spiritual legitimacy within Javanese culture and cosmology.
-
D.
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.
-
E.
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.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.