Triple
T26959041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mallikarjuna Swamy Temple |
E678984
|
entity |
| Predicate | shaktiPeethaGoddess |
P67533
|
FINISHED |
| Object | Bhramaramba |
—
|
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: Bhramaramba | Statement: [Mallikarjuna Swamy Temple, shaktiPeethaGoddess, Bhramaramba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shaktiPeethaGoddess Context triple: [Mallikarjuna Swamy Temple, shaktiPeethaGoddess, Bhramaramba]
-
A.
shaktiPeethaStatus
Indicates the status or classification of a site with respect to being recognized as a Shakti Peetha.
-
B.
viewsShaktiAs
chosen
Indicates perceiving or regarding someone or something specifically as Shakti, or as an embodiment or manifestation of Shakti.
-
C.
isKuldeviFor
Indicates a relationship where a particular goddess is revered as the ancestral or family deity (kuldevi) for a specific person, family, or lineage.
-
D.
hasNumberOfDivyaDesams
Indicates the specific count of Divya Desams associated with a given entity.
-
E.
associatedFormOfShiva
Indicates a relationship where one entity is a particular form, aspect, or manifestation that is traditionally associated with the deity Shiva.
- F. None of above.
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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620eadb4c8190bdfec5d1d5f7fdc1 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:29 a.m.