Triple

T20354521
Position Surface form Disambiguated ID Type / Status
Subject Ruma E496106 entity
Predicate family P566 FINISHED
Object Sugriva 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: Sugriva | Statement: [Ruma, family, Sugriva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sugriva
Context triple: [Ruma, family, Sugriva]
  • 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. Jambavan
    Jambavan is a wise and powerful bear-king from Hindu mythology, renowned for his role in the Ramayana and as a devoted ally of Lord Rama.
  • C. Anjaneya
    Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
  • D. Yuyudhana
    Yuyudhana, better known as Satyaki, is a prominent Yadava warrior and ally of the Pandavas in the Indian epic Mahabharata.
  • E. Vibhishana
    Vibhishana is a virtuous rakshasa prince in the Hindu epic Ramayana, known for abandoning his brother Ravana to ally with Rama and uphold dharma.
  • 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.