Triple
T4955860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murugan |
E111277
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Devasena |
E161608
|
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: Devasena | Statement: [Murugan, spouse, Devasena]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Devasena Context triple: [Murugan, spouse, Devasena]
-
A.
Devasena
chosen
Devasena is a Hindu goddess known as one of the wives of the war god Kartikeya, often associated with valor and divine grace.
-
B.
Vidyavati
Vidyavati is an Indian woman whose given name is associated with the full name Vidyavati Kaur.
-
C.
Chitrangada
Chitrangada is a warrior princess from the Indian epic Mahabharata, known as one of Arjuna’s wives and the daughter of the king of Manipur.
-
D.
Devi
Devi is the supreme goddess in Hinduism, embodying the divine feminine power (Shakti) in its many forms such as Durga, Parvati, Lakshmi, and Saraswati.
-
E.
Lalita Tripurasundari
Lalita Tripurasundari is a principal Hindu goddess of the Sri Vidya tradition, revered as the supremely beautiful and benevolent form of the Divine Mother who governs creation, preservation, and dissolution.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71babb44819085b4cd4864433e79 |
completed | March 20, 2026, 4:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf06982c5081908c275019c5d6b1c1 |
completed | March 21, 2026, 8:59 p.m. |
Created at: March 20, 2026, 1:32 p.m.