Triple

T4710447
Position Surface form Disambiguated ID Type / Status
Subject Lake Rakshastal E104494 entity
Predicate associatedWith P37 FINISHED
Object Ravana E112600 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: Ravana | Statement: [Lake Rakshastal, associatedWith, Ravana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ravana
Context triple: [Lake Rakshastal, associatedWith, Ravana]
  • A. Ravana chosen
    Ravana is the ten-headed demon king of Lanka in Hindu mythology, best known as the powerful antagonist of the epic Ramayana.
  • B. Andhaka
    Andhaka is a prominent clan within the ancient Yadava lineage of Hindu tradition, often associated with the family and kingdom of Krishna.
  • C. 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.
  • D. Hiranyakashipu
    Hiranyakashipu is a powerful demon king from Hindu mythology, best known as the tyrannical father of Prahlada and the antagonist slain by Vishnu’s Narasimha avatar.
  • E. Ghatotkacha
    Ghatotkacha is a powerful, magic-wielding rakshasa warrior from the Mahabharata, famed for his crucial role and heroic death in the Kurukshetra War.
  • 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_69bd43eac3c08190af7e4020c6c3704c completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd63ee712c81908da60aa0df58efe0 completed March 20, 2026, 3:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69be1078784c81908e9a3fd0b168cadc completed March 21, 2026, 3:28 a.m.
Created at: March 20, 2026, 1:17 p.m.