Triple

T18441057
Position Surface form Disambiguated ID Type / Status
Subject Vrishni E450526 entity
Predicate relatedClan P1915 FINISHED
Object Andhaka 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: Andhaka | Statement: [Vrishni, relatedClan, Andhaka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Andhaka
Context triple: [Vrishni, relatedClan, Andhaka]
  • A. Andhaka chosen
    Andhaka is a prominent clan within the ancient Yadava lineage of Hindu tradition, often associated with the family and kingdom of Krishna.
  • B. Bakasura
    Bakasura is a fearsome demon from Hindu mythology, known for his immense strength, cannibalistic nature, and defeat at the hands of the Pandava hero Bhima in the Mahabharata.
  • C. Ghatotkacha
    Ghatotkacha is a powerful, magic-wielding rakshasa warrior from the Mahabharata, famed for his crucial role and heroic death in the Kurukshetra War.
  • D. Banasura
    Banasura is a powerful asura king in Hindu mythology, best known for his thousand arms and his battle with Krishna over his daughter Usha.
  • E. Mahishasura
    Mahishasura is a powerful buffalo demon in Hindu mythology, best known as the formidable adversary slain by the goddess Durga in a legendary cosmic battle.
  • 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51c10a86c819091196968b648fc92 completed April 19, 2026, 6:16 p.m.
Created at: April 10, 2026, 11:30 a.m.