Triple
T34432927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahamastakabhisheka |
E883874
|
entity |
| Predicate | relatedRitualType |
P76648
|
FINISHED |
| Object | abhisheka |
—
|
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: abhisheka | Statement: [Mahamastakabhisheka, relatedRitualType, abhisheka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedRitualType Context triple: [Mahamastakabhisheka, relatedRitualType, abhisheka]
-
A.
relatedRitual
Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
-
B.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
C.
ritualCategory
chosen
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
D.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
-
E.
associatedRitualPrivilege
Indicates a relationship where a specific ritual is linked to a particular privilege granted or recognized in connection with that 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.