Triple
T16857837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daksha |
E409831
|
entity |
| Predicate | reignedIn |
P29663
|
FINISHED |
| Object | Mataram |
E84644
|
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: Mataram | Statement: [Daksha, reignedIn, Mataram]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mataram Context triple: [Daksha, reignedIn, Mataram]
-
A.
Mataram
chosen
Mataram was the principal urban and political center of the early Javanese Medang Kingdom, serving as a key hub of power and culture in central Java.
-
B.
Mataram
Mataram is the capital and largest city of the Indonesian province of West Nusa Tenggara, located on the island of Lombok.
-
C.
Semarapura
Semarapura is the capital town of Bali’s Klungkung Regency, known for its traditional Balinese culture, historic royal court, and vibrant arts and markets.
-
D.
Bima City
Bima City is an urban municipality on the eastern part of Sumbawa Island in Indonesia, serving as a regional economic and cultural center.
-
E.
Amlapura
Amlapura is a town in eastern Bali, Indonesia, known as the main urban and cultural hub of the surrounding Karangasem area.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37ef4748190b149d98fc0ab4205 |
completed | April 18, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb25300c8190a352037c21c244bd |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:24 a.m.