Triple

T2162411
Position Surface form Disambiguated ID Type / Status
Subject Ramleela E46830 entity
Predicate mainCharacter P1183 FINISHED
Object Hanuman E21412 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: Hanuman | Statement: [Ramleela, mainCharacter, Hanuman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hanuman
Context triple: [Ramleela, mainCharacter, Hanuman]
  • A. Hanuman chosen
    Hanuman is a revered Hindu deity known for his immense strength, unwavering devotion to Lord Rama, and central role in the epic Ramayana.
  • B. 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.
  • C. Narasimha
    Narasimha is the fierce man-lion incarnation of the Hindu god Vishnu, known for destroying the demon king Hiranyakashipu to protect his devotee Prahlada.
  • D. 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.
  • E. Balarama
    Balarama is a major Hindu deity revered as the elder brother of Krishna, known for his immense strength and role in supporting and protecting dharma.
  • 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_69a88a184cbc8190877791f6552c2484 completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abbe8b9c0881908373eabc7f81c394 completed March 7, 2026, 5:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae5d98286c8190a6890e2c7daa10b5 completed March 9, 2026, 5:41 a.m.
Created at: March 4, 2026, 7:45 p.m.