Triple
T21562070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parshvanatha |
E532061
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object |
Ashvasena
Ashvasena is known in Jain tradition as the father of Parshvanatha, the 23rd Tirthankara.
|
E1490955
|
NE FINISHED |
How this triple was built (4 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: Ashvasena | Statement: [Parshvanatha, father, Ashvasena]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashvasena Context triple: [Parshvanatha, father, Ashvasena]
-
A.
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.
-
B.
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.
-
C.
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.”
-
D.
Surasena
Surasena was an ancient Indian kingdom and one of the sixteen Mahajanapadas, centered around its capital Mathura in the northern Indian subcontinent.
-
E.
Ugrasena
Ugrasena is a legendary king in Hindu mythology, known as a ruler of the Yadava clan and the grandfather of Krishna.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Ashvasena Triple: [Parshvanatha, father, Ashvasena]
Generated description
Ashvasena is known in Jain tradition as the father of Parshvanatha, the 23rd Tirthankara.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Ashvasena Target entity description: Ashvasena is known in Jain tradition as the father of Parshvanatha, the 23rd Tirthankara.
-
A.
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.
-
B.
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.
-
C.
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.”
-
D.
Surasena
Surasena was an ancient Indian kingdom and one of the sixteen Mahajanapadas, centered around its capital Mathura in the northern Indian subcontinent.
-
E.
Ugrasena
Ugrasena is a legendary king in Hindu mythology, known as a ruler of the Yadava clan and the grandfather of Krishna.
- F. None of above. chosen
Provenance (5 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e3e2348190b5c3b66cdc871e6e |
completed | April 27, 2026, 3:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a09eeeb5c6081908267b5825acddad5 |
completed | May 17, 2026, 4:38 p.m. |
| NEDg | Description generation | batch_6a09f3334a088190b16c3715c786f4e2 |
completed | May 17, 2026, 4:56 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a09f40c04a48190b60c80f44759b295 |
completed | May 17, 2026, 4:59 p.m. |
Created at: April 16, 2026, 6:29 p.m.