Triple

T18737751
Position Surface form Disambiguated ID Type / Status
Subject Yayati E458208 entity
Predicate father P120 FINISHED
Object Nahusha 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: Nahusha | Statement: [Yayati, father, Nahusha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nahusha
Context triple: [Yayati, father, Nahusha]
  • A. Nahusha chosen
    Nahusha is a legendary king from Hindu mythology who briefly ruled the heavens in place of Indra before being cursed and cast down for his arrogance.
  • B. Vishrava
    Vishrava is a revered sage in Hindu mythology, best known as the father of the demon king Ravana and his giant brother Kumbhakarna in the Ramayana.
  • C. Andhaka
    Andhaka is a prominent clan within the ancient Yadava lineage of Hindu tradition, often associated with the family and kingdom of Krishna.
  • D. Adhiratha
    Adhiratha is a charioteer in the Mahabharata who finds and raises the abandoned infant Karna as his own son.
  • E. Bhurishravas
    Bhurishravas is a warrior prince from the Mahabharata epic, known as a formidable Kaurava ally who meets his end on the battlefield of Kurukshetra.
  • 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_69d8d394dc308190b6725073f5db324c completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5768b80ac8190bc05628d64f86fc9 completed April 20, 2026, 12:42 a.m.
Created at: April 10, 2026, 11:51 a.m.