Triple
T31706927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanwariya |
E809204
|
entity |
| Predicate | ritualGoal |
P136395
|
FINISHED |
| Object | to pour Ganga water on Shiva linga |
—
|
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: to pour Ganga water on Shiva linga | Statement: [Kanwariya, ritualGoal, to pour Ganga water on Shiva linga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualGoal Context triple: [Kanwariya, ritualGoal, to pour Ganga water on Shiva linga]
-
A.
hasRitualGoal
chosen
Indicates that an action, practice, or ritual is performed with the specific purpose of achieving a particular ritualistic outcome or objective.
-
B.
ritualPurpose
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
-
C.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
D.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
-
E.
ritualOutcome
Indicates the result or consequence produced by performing a particular ritual.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:14 p.m.