Triple
T20354531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruma |
E496106
|
entity |
| Predicate | spouseTitle |
P2097
|
FINISHED |
| Object | KingSugriva |
—
|
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: KingSugriva | Statement: [Ruma, spouseTitle, KingSugriva]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KingSugriva Context triple: [Ruma, spouseTitle, KingSugriva]
-
A.
Sugriva
chosen
Sugriva is the exiled monkey king in the Hindu epic Ramayana who allies with Rama to defeat the demon king Ravana and reclaim his own throne.
-
B.
King Virata
King Virata is the ruler of the Matsya kingdom in the Mahabharata, best known for sheltering the Pandavas in disguise during their final year of exile.
-
C.
Drupada
Drupada is a king in the Indian epic Mahabharata, best known as the ruler of Panchala and the father of Draupadi and Dhrishtadyumna.
-
D.
Jayadratha
Jayadratha is a king from the Indian epic Mahabharata, best known for his role in the death of Abhimanyu and his subsequent slaying by Arjuna.
-
E.
King of Panchala
King of Panchala is a royal title in the Indian epic Mahabharata, most notably held by Drupada, the ruler of the ancient kingdom of Panchala.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67852ca9881908a5af18005639859 |
completed | April 20, 2026, 7:02 p.m. |
Created at: April 16, 2026, 11:25 a.m.