Triple

T20054471
Position Surface form Disambiguated ID Type / Status
Subject Draupadi E499290 entity
Predicate son P25213 FINISHED
Object Srutasena 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: Srutasena | Statement: [Draupadi, son, Srutasena]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Srutasena
Context triple: [Draupadi, son, Srutasena]
  • A. Srutasena chosen
    Srutasena is a lesser-known prince in the Indian epic Mahabharata, recognized as one of the sons of Draupadi and the Pandava hero Bhima.
  • B. Vishnukumara
    Vishnukumara was a 10th-century Khmer official associated with the construction and patronage of the intricately carved Banteay Srei temple in Cambodia.
  • C. Gunabhadra
    Gunabhadra was a prominent Jain poet and scholar associated with the Rashtrakuta dynasty, known for his significant contributions to medieval Indian religious and literary traditions.
  • D. Narasinga
    Narasinga was a prominent monarch of the Vemulavada Chalukya dynasty in early medieval South India, known for consolidating regional power and patronizing Hindu temples and culture.
  • E. Raghoba
    Raghoba, also known as Raghunath Rao, was an 18th-century Maratha leader and briefly a claimant to the Peshwa title in the Maratha Empire.
  • 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_69da6276bcf48190aabbf279192a5fb4 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66331c7488190840d43792ff09977 completed April 20, 2026, 5:32 p.m.
Created at: April 11, 2026, 3:38 p.m.