Triple

T19730849
Position Surface form Disambiguated ID Type / Status
Subject Prishati E473848 entity
Predicate spouse P13 FINISHED
Object Drupada 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: Drupada | Statement: [Prishati, spouse, Drupada]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Drupada
Context triple: [Prishati, spouse, Drupada]
  • A. Drupada chosen
    Drupada is a king in the Indian epic Mahabharata, best known as the ruler of Panchala and the father of Draupadi and Dhrishtadyumna.
  • B. Jayadratha
    Jayadratha is a king from the Indian epic Mahabharata, best known for his role in the death of Abhimanyu and his subsequent slaying by Arjuna.
  • C. Shakuni
    Shakuni is a key antagonist in the Indian epic Mahabharata, known as the cunning prince of Gandhara whose deceitful schemes and manipulation of dice play a central role in triggering the Kurukshetra war.
  • D. Ugrasena
    Ugrasena is a legendary king in Hindu mythology, known as a ruler of the Yadava clan and the grandfather of Krishna.
  • E. Suryaputra
    Suryaputra is an epithet of the legendary warrior Karna from the Indian epic Mahabharata, highlighting his divine parentage as the son of the sun god Surya.
  • 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e649fbeaf081909e9356229eaf84dd completed April 20, 2026, 3:45 p.m.
Created at: April 10, 2026, 1:47 p.m.