Triple
T18737659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savitrī |
E458206
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Aśvapati |
—
|
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: Aśvapati | Statement: [Savitrī, father, Aśvapati]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aśvapati Context triple: [Savitrī, father, Aśvapati]
-
A.
Aśvajit
Aśvajit was one of the Buddha’s early disciples, traditionally remembered as the monk whose brief teaching led to the conversion of Śāriputra.
-
B.
Ashwapati
chosen
Ashwapati is a king in the Hindu epic Ramayana, best known as the ruler of the kingdom of Kekaya and the father of Queen Kaikeyi.
-
C.
Asvabhahu
Asvabhahu was a literary pseudonym used by King Vajiravudh (Rama VI) of Siam for some of his written works.
-
D.
Puspadanta
Puspadanta was a prominent Jain monk and poet known for composing important Apabhramsha-language works such as the Mahapurana.
-
E.
Dronasimha
Dronasimha was a ruler of the Maitraka dynasty of western India, known from inscriptions as one of the early kings who helped consolidate Maitraka power in the region.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5768b80ac8190bc05628d64f86fc9 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 10, 2026, 11:51 a.m.