Triple
T17096338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kameswara |
E414860
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Jayabaya |
E89809
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Jayabaya | Statement: [Kameswara, successor, Jayabaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jayabaya Context triple: [Kameswara, successor, Jayabaya]
-
A.
Jayabaya
chosen
Jayabaya was a legendary 12th-century king of the Kediri Kingdom in Java, renowned in Indonesian history and folklore for his just rule and prophetic visions.
-
B.
Samaratungga
Samaratungga was a 9th-century Javanese king of the Sailendra dynasty best known for commissioning the construction of the monumental Borobudur Buddhist temple in Central Java.
-
C.
Prabu Padjadjaran
Prabu Padjadjaran is a legendary Sundanese king associated with the historical Padjadjaran kingdom in West Java, Indonesia.
-
D.
Mpu Sindok
Mpu Sindok was a 10th-century Javanese king who relocated the Medang Kingdom’s power center to East Java and founded the Isyana dynasty.
-
E.
Prabu
Prabu is a royal title historically used for kings or rulers in the Sundanese Kingdom of West Java, Indonesia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfdc9c88190b4e75bbdf4105c1e |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0139fbcbc08190be2a96d03daf0384 |
completed | May 11, 2026, 2:07 a.m. |
Created at: April 10, 2026, 5:35 a.m.