Triple
T36562196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhadrakali Temple |
E901868
|
entity |
| Predicate | languageUsedForRituals |
P59986
|
FINISHED |
| Object | Sanskrit |
—
|
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: Sanskrit | Statement: [Bhadrakali Temple, languageUsedForRituals, Sanskrit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedForRituals Context triple: [Bhadrakali Temple, languageUsedForRituals, Sanskrit]
-
A.
languageUsedInRituals
chosen
Indicates that a particular language is employed as the medium of speech, chant, or recitation during specific rituals or ceremonial practices.
-
B.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
C.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
D.
ritualSignificance
Indicates that something holds special importance or meaning within a ritual or ceremonial context.
-
E.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a013632a3048190b05716d803f34716 |
completed | May 11, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_6a01309582e48190a05d47d96ffb7a46 |
completed | May 11, 2026, 1:27 a.m. |
Created at: May 3, 2026, 4:11 p.m.