Triple
T23385268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushyamitra Shunga |
E593859
|
entity |
| Predicate | fatherOf |
P120
|
FINISHED |
| Object | Agnimitra |
—
|
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: Agnimitra | Statement: [Pushyamitra Shunga, fatherOf, Agnimitra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Agnimitra Context triple: [Pushyamitra Shunga, fatherOf, Agnimitra]
-
A.
Agnimitra
chosen
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.”
-
B.
Janamejaya
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.
-
C.
Meghnad
Meghnad is a given name most notably associated with Indian astrophysicist Meghnad Saha, renowned for his pioneering work on thermal ionization and stellar spectra.
-
D.
Meghnad
Meghnad is a legendary warrior prince from the Indian epic Ramayana, renowned as the valiant son of Ravana and a formidable adversary of Rama’s forces.
-
E.
Ashvasena
Ashvasena is known in Jain tradition as the father of Parshvanatha, the 23rd Tirthankara.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a497661c8190b52fa27419594989 |
completed | April 29, 2026, 6:26 a.m. |
Created at: April 17, 2026, 5:35 p.m.