Triple

T5375621
Position Surface form Disambiguated ID Type / Status
Subject Srutakarma E108951 entity
Predicate relativeOf P367 FINISHED
Object Sahadeva E116823 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: Sahadeva | Statement: [Srutakarma, relativeOf, Sahadeva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sahadeva
Context triple: [Srutakarma, relativeOf, Sahadeva]
  • A. Sahadeva chosen
    Sahadeva is one of the five Pandava brothers in the Indian epic Mahabharata, renowned for his wisdom, knowledge of astrology, and loyalty.
  • B. Shatrughna
    Shatrughna is a prince of Ayodhya in the Hindu epic Ramayana, known as the devoted younger brother of Rama and the twin of Lakshmana.
  • C. Bhima
    Bhima is a major river in western India that flows through the states of Maharashtra, Karnataka, and Telangana before joining the Krishna River.
  • D. Bhima
    Bhima is a powerful warrior prince from the Indian epic Mahabharata, renowned for his immense strength, loyalty, and pivotal role among the Pandava brothers.
  • E. Pradyumna
    Pradyumna is a prominent figure in Hindu mythology, known as the son of Krishna and Rukmini and considered an incarnation of the love god Kamadeva.
  • 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_69bd440c77948190aad2a5f39b7b80f5 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd86aed2a8819089d9e699f53563db completed March 20, 2026, 5:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfba21331481908fc43a47f06d7c87 completed March 22, 2026, 9:45 a.m.
Created at: March 20, 2026, 2:03 p.m.