Triple
T18854168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Srikalahasteeswara Temple |
E461125
|
entity |
| Predicate | hasSpecialPuja |
P4193
|
FINISHED |
| Object | Rahu Ketu Sarpa Dosha puja |
—
|
LITERAL 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: Rahu Ketu Sarpa Dosha puja | Statement: [Srikalahasteeswara Temple, hasSpecialPuja, Rahu Ketu Sarpa Dosha puja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialPuja Context triple: [Srikalahasteeswara Temple, hasSpecialPuja, Rahu Ketu Sarpa Dosha puja]
-
A.
hasPrayerRite
Indicates that one entity is associated with, follows, or practices a particular prayer rite or liturgical form.
-
B.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
C.
performedYajnaFor
Indicates that one entity conducted or officiated a yajna (a Vedic ritual sacrifice) on behalf of or in honor of another entity.
-
D.
hasPilgrimageActivity
Indicates that an entity engages in, organizes, or is associated with a religious pilgrimage activity.
-
E.
hasRitual
chosen
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05b4d8881909af0238f451b0e31 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.