Triple
T5117644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugriva |
E115376
|
entity |
| Predicate | kingdom |
P567
|
FINISHED |
| Object | Kishkindha |
E124411
|
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: Kishkindha | Statement: [Sugriva, kingdom, Kishkindha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kishkindha Context triple: [Sugriva, kingdom, Kishkindha]
-
A.
Kishkindha
chosen
Kishkindha is the mythical monkey kingdom ruled by Sugriva in the Indian epic Ramayana, where Rama forms an alliance with the vanara army to search for Sita.
-
B.
Kosala
Kosala is an ancient Indian kingdom in Hindu epic tradition, most prominently known as the realm ruled by Lord Rama with its capital at Ayodhya.
-
C.
Singhwara
Singhwara is a town located in the Darbhanga district of the Indian state of Bihar.
-
D.
Dashagriva
Dashagriva is an epithet of the demon-king Ravana from the Hindu epic Ramayana, highlighting his legendary form with ten heads.
-
E.
Maddur
Maddur is a town in Karnataka, India, known for its location between Bengaluru and Mysuru and its popular local snack, Maddur vada.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd77ce1ea48190b283cae7bb9b72eb |
completed | March 20, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bec4a6a7988190b9beec3f0d9494d1 |
completed | March 21, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:41 p.m.