Triple
T25693358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrinathji |
E644254
|
entity |
| Predicate | worshipEmphasis |
P11149
|
FINISHED |
| Object | bhakti (devotion) |
—
|
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: bhakti (devotion) | Statement: [Shrinathji, worshipEmphasis, bhakti (devotion)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipEmphasis Context triple: [Shrinathji, worshipEmphasis, bhakti (devotion)]
-
A.
worshipFocus
Indicates that one entity directs religious reverence, devotion, or adoration toward another as the primary object of worship.
-
B.
worshipPurpose
Indicates that an act of worship is performed with a specific intended purpose, goal, or reason in mind.
-
C.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
D.
worshipType
chosen
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
E.
worshipScope
Indicates the range or extent within which worship, veneration, or religious devotion is directed or practiced.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 8:31 p.m.