Triple
T22591174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu pantheon |
E564951
|
entity |
| Predicate | hasDeity |
P5606
|
FINISHED |
| Object | Chamunda |
—
|
NE NERFINISHED |
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: Chamunda | Statement: [Hindu pantheon, hasDeity, Chamunda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chamunda Context triple: [Hindu pantheon, hasDeity, Chamunda]
-
A.
Chamunda
chosen
Chamunda is a fierce and terrifying aspect of the Hindu goddess Kali, associated with destruction of evil, cremation grounds, and protective wrath.
-
B.
Chamunda Devi
Chamunda Devi is a fierce Hindu goddess, revered as a protective form of Durga and especially worshipped as the patron deity of the royal family of Jodhpur.
-
C.
Kamakshi
Kamakshi is a revered form of the Hindu goddess Parvati, worshipped especially in Kanchipuram as a central deity of Shakta tradition.
-
D.
Marudevi
Marudevi is revered in Jain tradition as the mother of the first Tirthankara, Rishabhanatha, and an important figure in early Jain spiritual narratives.
-
E.
Chhinnamasta
Chhinnamasta is a fierce and self-decapitated Hindu goddess associated with the Mahavidyas, symbolizing the paradoxical unity of life, death, and sexual energy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f16160651081909d23735336fd7a16 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 2:48 p.m.