Triple
T923532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiva |
E19933
|
entity |
| Predicate | consort |
P13
|
FINISHED |
| Object | Parvati |
E20132
|
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: Parvati | Statement: [Shiva, consort, Parvati]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parvati Context triple: [Shiva, consort, Parvati]
-
A.
Devi
chosen
Devi is the supreme goddess in Hinduism, embodying the divine feminine power (Shakti) in its many forms such as Durga, Parvati, Lakshmi, and Saraswati.
-
B.
Gayatri
Gayatri is a highly revered Vedic poetic meter consisting of three lines of eight syllables each, widely used in Hindu sacred hymns and mantras.
-
C.
goddess Mumbadevi
Goddess Mumbadevi is a local Hindu deity revered as the patron goddess of Mumbai, with a historic temple in the city that is central to its cultural and religious identity.
-
D.
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.
-
E.
Jambavati
Jambavati is a prominent queen of the Hindu deity Krishna, revered in scripture as one of his principal consorts and the daughter of the bear-king Jambavan.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b314f6fc81908a3ccc2e741e3c2b |
completed | March 1, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac119792d48190b5e942f2dd3fd34e |
completed | March 7, 2026, 11:52 a.m. |
Created at: March 1, 2026, 7:40 p.m.