Triple

T20551700
Position Surface form Disambiguated ID Type / Status
Subject Bhagwan Dattatreya E504610 entity
Predicate hasSibling P363 FINISHED
Object Durvasa 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: Durvasa | Statement: [Bhagwan Dattatreya, hasSibling, Durvasa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Durvasa
Context triple: [Bhagwan Dattatreya, hasSibling, Durvasa]
  • A. Durvasa chosen
    Durvasa is a hot-tempered sage from Hindu mythology, renowned for his quick anger and powerful curses that significantly influence many legendary tales.
  • B. Dashagriva
    Dashagriva is an epithet of the demon-king Ravana from the Hindu epic Ramayana, highlighting his legendary form with ten heads.
  • C. Vrikodara
    Vrikodara is a famous epithet of Bhima, the mighty Pandava hero of the Indian epic Mahabharata, highlighting his immense strength and voracious appetite.
  • D. Mahāraurava
    Mahāraurava is a particularly terrifying hell realm in Hindu cosmology, associated with intense suffering for grievous sinners.
  • E. Mandhata
    Mandhata is a legendary king of ancient India, celebrated in Hindu tradition as a powerful and virtuous ruler of the Solar dynasty.
  • 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_69e0b4b52c048190952b4d0f430813a3 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5d98c348190ac516bc2df59d878 completed April 20, 2026, 10:16 p.m.
Created at: April 16, 2026, 11:38 a.m.