Triple
T19056922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santoshi Mata |
E466420
|
entity |
| Predicate | devoteeExpectation |
P134929
|
FINISHED |
| Object | fulfillment of wishes |
—
|
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: fulfillment of wishes | Statement: [Santoshi Mata, devoteeExpectation, fulfillment of wishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devoteeExpectation Context triple: [Santoshi Mata, devoteeExpectation, fulfillment of wishes]
-
A.
devoteesSeek
Indicates that devoted followers actively seek out, pursue, or strive to approach the object of their devotion.
-
B.
devotionPracticedBy
Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
-
C.
receivesDevoteesFrom
Indicates that an entity (such as a place, person, or institution) is the destination to which devotees come or are directed from another entity.
-
D.
devoteesCallDeity
Indicates that devotees address, refer to, or invoke a particular deity by a specific name or title.
-
E.
pursuesDeity
Indicates that one entity actively seeks, follows, or strives to attain or engage with a deity.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc067f788190b3b149dfee370435 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.