Triple
T5248252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pradosha vrata |
E118515
|
entity |
| Predicate | templePractice |
P61723
|
FINISHED |
| Object | special evening puja in Shiva temples |
—
|
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: special evening puja in Shiva temples | Statement: [Pradosha vrata, templePractice, special evening puja in Shiva temples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templePractice Context triple: [Pradosha vrata, templePractice, special evening puja in Shiva temples]
-
A.
postTemplePractice
Indicates a practice, behavior, or ritual that occurs after activities in or associated with a temple have concluded.
-
B.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
C.
templeOpening
Indicates that a temple begins operating or becomes accessible for worship, visitation, or related activities.
-
D.
pilgrimagePractice
Indicates that an entity engages in, prescribes, or is associated with the religious act of undertaking a pilgrimage as a spiritual practice.
-
E.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b77165c8190bd1ce8a197cef226 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd787975788190848ffbac87896efe |
completed | March 20, 2026, 4:40 p.m. |
Created at: March 20, 2026, 1:50 p.m.