Triple

T992043
Position Surface form Disambiguated ID Type / Status
Subject Hanuman E21412 entity
Predicate associatedWith P37 FINISHED
Object Sugriva E115376 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: Sugriva | Statement: [Hanuman, associatedWith, Sugriva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sugriva
Context triple: [Hanuman, associatedWith, 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. 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.
  • C. Babruvahana
    Babruvahana is a character in the Indian epic Mahabharata, known as the son of the Pandava prince Arjuna and the princess Chitrangada, and as a skilled warrior and later ruler of Manipura.
  • D. Rama
    Rama is a major Hindu deity and the virtuous prince-king of Ayodhya, revered as the seventh avatar of Vishnu and hero of the epic Ramayana.
  • E. Sanjaya
    Sanjaya was an early Javanese king traditionally regarded as the founder of the Mataram (Medang) Kingdom and the Sanjaya dynasty in Central Java.
  • 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_69a493c476b48190b41fc5e793171cc6 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b4c25e5081909ff1ada6b8bf617a completed March 1, 2026, 9:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac4c0bda208190b10b238a30466ea6 completed March 7, 2026, 4:02 p.m.
Created at: March 1, 2026, 7:41 p.m.