Triple

T4936587
Position Surface form Disambiguated ID Type / Status
Subject Prativindhya E110825 entity
Predicate sibling P363 FINISHED
Object Shrutasena E476796 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: Shrutasena | Statement: [Prativindhya, sibling, Shrutasena]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shrutasena
Context triple: [Prativindhya, sibling, Shrutasena]
  • 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. Ugrasena
    Ugrasena is a legendary king in Hindu mythology, known as a ruler of the Yadava clan and the grandfather of Krishna.
  • C. Akrura
    Akrura is a revered figure in Hindu mythology, known as a devout Yadava charioteer and ally of Krishna who played a key role in bringing him to Mathura.
  • D. Babruvahana
    Babruvahana is a character in the Indian epic Mahabharata, known as the son of the Pandava prince Arjuna and the princess Chitrangada, and as a skilled warrior and later ruler of Manipura.
  • E. Pavanputra
    Pavanputra is a revered epithet of the Hindu deity Hanuman, highlighting his divine parentage as the son of the wind god.
  • 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_69bd4415eee08190bdce70276e56a5b4 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd7085b1dc819099408f6503f0210f completed March 20, 2026, 4:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69be923eac848190b8511b8027c87ff3 completed March 21, 2026, 12:42 p.m.
Created at: March 20, 2026, 1:30 p.m.