Triple
T21929545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surakarta Hadiningrat |
E541531
|
entity |
| Predicate | hasRulerTitle |
P17756
|
FINISHED |
| Object | Susuhunan |
—
|
NE NERFINISHED |
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: Susuhunan | Statement: [Surakarta Hadiningrat, hasRulerTitle, Susuhunan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Susuhunan Context triple: [Surakarta Hadiningrat, hasRulerTitle, Susuhunan]
-
A.
Susuhunan
chosen
Susuhunan is the royal title used by the monarchs of the Surakarta Sunanate in Central Java, Indonesia.
-
B.
Sadanaru
Sadanaru is a Japanese given name historically borne by members of the imperial family, including Prince Fushimi Sadanaru.
-
C.
Simuka
Simuka was the founder and one of the earliest known kings of the Satavahana dynasty in ancient India.
-
D.
Sungguminasa
Sungguminasa is the administrative and urban center of Gowa Regency in South Sulawesi, Indonesia.
-
E.
Suseo
Suseo is a neighborhood in southeastern Seoul, South Korea, known for its major high-speed rail station that links the capital to cities such as Busan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123fdd88081909dc7d4a05fb0ee35 |
completed | April 28, 2026, 9:17 p.m. |
Created at: April 16, 2026, 7:47 p.m.