Triple
T4522764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yashoda |
E103305
|
entity |
| Predicate | nameVariant |
P744
|
FINISHED |
| Object | Yashodha |
E103305
|
NE FINISHED |
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: Yashodha | Statement: [Yashoda, nameVariant, Yashodha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yashodha Context triple: [Yashoda, nameVariant, Yashodha]
-
A.
Yaśodharā
Yaśodharā is traditionally regarded as the wife of Prince Siddhartha Gautama (who became the Buddha) and the mother of his son Rāhula in Buddhist narratives.
-
B.
Yashoda
chosen
Yashoda is the loving foster mother of the Hindu deity Krishna, revered for her deep maternal devotion and prominent role in his childhood stories.
-
C.
Yashoda
Yashoda was the wife of Mahavira, the 24th Tirthankara of Jainism, and is traditionally regarded as his consort before he renounced worldly life.
-
D.
Devaki
Devaki is a revered figure in Hindu mythology best known as the mother of Lord Krishna.
-
E.
Rukmini
Rukmini is a principal queen of the Hindu god Krishna, revered as an incarnation of the goddess Lakshmi and celebrated for her devotion and role in Krishna’s life.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd574d7c2481909049955ca47613a6 |
completed | March 20, 2026, 2:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdd37f7ed48190ae0a82597aafc66e |
completed | March 20, 2026, 11:08 p.m. |
Created at: March 20, 2026, 1:02 p.m.