Triple
T19204828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahagauri |
E480203
|
entity |
| Predicate | benefitOfWorship |
P57116
|
FINISHED |
| Object | removal of sins |
—
|
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: removal of sins | Statement: [Mahagauri, benefitOfWorship, removal of sins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitOfWorship Context triple: [Mahagauri, benefitOfWorship, removal of sins]
-
A.
worshipBenefit
chosen
Indicates that one entity gains a spiritual, social, or material advantage as a result of worship directed toward another entity.
-
B.
goalOfWorship
Indicates that one entity is the intended object or focus of another entity’s worship or devotional practice.
-
C.
spiritualBenefit
Indicates a relationship where one entity provides, enhances, or is associated with a positive spiritual gain, growth, or advantage for another entity.
-
D.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
E.
worshipPrinciple
Indicates that one entity regards another as sacred or divine and performs acts of reverence, devotion, or religious honor toward it.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f99cc39c81909499b8d0b78b4665 |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:17 p.m.