Triple
T18476666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhrishtadyumna |
E451451
|
entity |
| Predicate | father |
P120
|
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: [Dhrishtadyumna, father, Drupada]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Drupada Context triple: [Dhrishtadyumna, father, 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.
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.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53063c0108190be71247567b5241b |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:35 a.m.