Triple
T5853333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skanda Purana |
E130089
|
entity |
| Predicate | associatedDeity |
P1481
|
FINISHED |
| Object | Skanda |
E31785
|
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: Skanda | Statement: [Skanda Purana, associatedDeity, Skanda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skanda Context triple: [Skanda Purana, associatedDeity, Skanda]
-
A.
Kartikeya
chosen
Kartikeya is a Hindu war god, traditionally depicted as a youthful, spear-wielding deity and revered as the son of Shiva and Parvati.
-
B.
Pradyumna
Pradyumna is a prominent figure in Hindu mythology, known as the son of Krishna and Rukmini and considered an incarnation of the love god Kamadeva.
-
C.
Rudra
Rudra is a fierce and storm-associated Vedic deity later identified with the Hindu god Shiva, known for his destructive and healing powers.
-
D.
Narasimha
Narasimha is the fierce man-lion incarnation of the Hindu god Vishnu, known for destroying the demon king Hiranyakashipu to protect his devotee Prahlada.
-
E.
Shanmukha
Shanmukha is a revered Hindu deity of war and victory, widely worshipped as the six-faced son of Shiva and Parvati.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c035529cf88190acc547ae839950e7 |
completed | March 22, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0bfd6cffc8190b65252f02055e89c |
completed | March 23, 2026, 4:21 a.m. |
Created at: March 22, 2026, 3:55 p.m.