Triple
T38313737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chitai Golu Devta Temple |
E1033766
|
entity |
| Predicate | devoteeAction |
P130883
|
FINISHED |
| Object | offer bells after wishes are fulfilled |
—
|
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: offer bells after wishes are fulfilled | Statement: [Chitai Golu Devta Temple, devoteeAction, offer bells after wishes are fulfilled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devoteeAction Context triple: [Chitai Golu Devta Temple, devoteeAction, offer bells after wishes are fulfilled]
-
A.
devoteesSeek
Indicates that devoted followers actively seek out, pursue, or strive to approach the object of their devotion.
-
B.
devoteesCallDeity
Indicates that devotees address, refer to, or invoke a particular deity by a specific name or title.
-
C.
devoteesPrayFor
Indicates that devoted followers direct prayers or supplications toward a person, entity, or cause on its behalf.
-
D.
devotionPracticedBy
chosen
Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
-
E.
effectOnDevotee
Indicates how an action, event, or entity influences or impacts a devotee.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.