Triple
T26959042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mallikarjuna Swamy Temple |
E678984
|
entity |
| Predicate | shaktiPeethaBodyPart |
P161732
|
FINISHED |
| Object | Neck of Sati |
—
|
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: Neck of Sati | Statement: [Mallikarjuna Swamy Temple, shaktiPeethaBodyPart, Neck of Sati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shaktiPeethaBodyPart Context triple: [Mallikarjuna Swamy Temple, shaktiPeethaBodyPart, Neck of Sati]
-
A.
shaktiPeethaStatus
Indicates the status or classification of a site with respect to being recognized as a Shakti Peetha.
-
B.
hasNumberOfDivyaDesams
Indicates the specific count of Divya Desams associated with a given entity.
-
C.
hasNumberOfJyotirlingas
Indicates the relationship specifying how many Jyotirlingas (sacred Shiva shrines) are associated with a given entity.
-
D.
positionInSriYantra
Indicates the specific spatial location or role that an element occupies within the geometric structure of the Sri Yantra.
-
E.
spiritualCenterOf
Indicates that one entity serves as the primary locus or focal point of spiritual life, practice, or significance for another entity or group.
- F. None of above. chosen
Provenance (4 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_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 6:29 a.m.