Triple
T11860982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virūḍhaka |
E282155
|
entity |
| Predicate | SanskritName |
P744
|
FINISHED |
| Object | Virūḍhaka |
E282155
|
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: Virūḍhaka | Statement: [Virūḍhaka, SanskritName, Virūḍhaka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Virūḍhaka Context triple: [Virūḍhaka, SanskritName, Virūḍhaka]
-
A.
Virūḍhaka
chosen
Virūḍhaka is one of the Four Heavenly Kings in Buddhist cosmology, traditionally regarded as the guardian of the southern direction and protector of the Dharma.
-
B.
Viradha
Viradha is a demon (rakshasa) in the Hindu epic Ramayana who confronts Rama, Sita, and Lakshmana in the Aranya Kanda during their forest exile.
-
C.
Vipākaśruta
Vipākaśruta is one of the canonical Jain Āgamas that focuses on the karmic consequences of actions and their results.
-
D.
Asvabhahu
Asvabhahu was a literary pseudonym used by King Vajiravudh (Rama VI) of Siam for some of his written works.
-
E.
Vichitravirya
Vichitravirya is a king from the Kuru dynasty in the Indian epic Mahabharata, known as the father of Dhritarashtra and Pandu and a key ancestral figure in the lineage leading to the Kauravas and Pandavas.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69b16bc8190999a0c1240f9ce6a |
completed | April 10, 2026, 7:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f43fc3f6688190aec5c0b481cfc77f |
completed | May 1, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:43 p.m.