Triple

T21772979
Position Surface form Disambiguated ID Type / Status
Subject Chiranjivi E537481 entity
Predicate hasMember P10 FINISHED
Object Bibhishana 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: Bibhishana | Statement: [Chiranjivi, hasMember, Bibhishana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bibhishana
Context triple: [Chiranjivi, hasMember, Bibhishana]
  • A. Indrajit
    Indrajit is a powerful warrior prince in the Hindu epic Ramayana, famed for his mastery of celestial weapons and for being the formidable son of the demon king Ravana.
  • B. Yudhajit
    Yudhajit is a lesser-known prince in the Ramayana, recognized as the brother of Queen Kaikeyi and thus an uncle of Bharata.
  • C. Vibhishana chosen
    Vibhishana is a virtuous rakshasa prince in the Hindu epic Ramayana, known for abandoning his brother Ravana to ally with Rama and uphold dharma.
  • D. Ugrasena
    Ugrasena is a legendary king in Hindu mythology, known as a ruler of the Yadava clan and the grandfather of Krishna.
  • E. 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.
  • 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_69e0c470759c819094a215757113562b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f031af6a488190a2dcebed43d199d4 completed April 28, 2026, 4:03 a.m.
Created at: April 16, 2026, 6:51 p.m.