Triple

T21319407
Position Surface form Disambiguated ID Type / Status
Subject Parikshit E525570 entity
Predicate fatherOf P120 FINISHED
Object Janamejaya 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: Janamejaya | Statement: [Parikshit, fatherOf, Janamejaya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Janamejaya
Context triple: [Parikshit, fatherOf, Janamejaya]
  • A. Janamejaya chosen
    Janamejaya is a legendary Kuru dynasty ruler from Indian epic tradition, known especially for performing a great snake sacrifice to avenge his father’s death.
  • B. Agnimitra
    Agnimitra was a prominent early ruler of the Shunga dynasty in ancient India, known from both historical records and Kalidasa’s Sanskrit play “Mālavikāgnimitram.”
  • C. जयद्रथ
    जयद्रथ महाभारत का एक पात्र था, जो कुरुक्षेत्र युद्ध में कौरव पक्ष का राजा और अर्जुन के पुत्र अभिमन्यु की मृत्यु के लिए कुख्यात माना जाता है।
  • D. King Shalya
    King Shalya is a prominent monarch in the Indian epic Mahabharata, known as the ruler of Madra and a formidable warrior who plays a complex role in the Kurukshetra War.
  • E. Ajaya
    Ajaya is an Indian given name, often used for both males and females, meaning "unconquered" or "invincible" in Sanskrit.
  • 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_69e0b51ad810819098c12392c8e55f6c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e77ecf12248190bb4172ad7416775e completed April 21, 2026, 1:42 p.m.
Created at: April 16, 2026, 4:38 p.m.