Triple
T17953096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saurism |
E448878
|
entity |
| Predicate | hasDevotionalForm |
P129877
|
FINISHED |
| Object | Surya bhakti (devotion to Surya) |
—
|
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: Surya bhakti (devotion to Surya) | Statement: [Saurism, hasDevotionalForm, Surya bhakti (devotion to Surya)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevotionalForm Context triple: [Saurism, hasDevotionalForm, Surya bhakti (devotion to Surya)]
-
A.
hasDevotionalFormula
Indicates a relationship where one entity includes, uses, or is associated with a specific devotional formula (such as a set religious phrase, prayer, or invocation).
-
B.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
C.
devotionalFormat
Indicates the specific structure or style in which a devotional practice, text, or activity is organized or presented.
-
D.
devotionalLanguageType
Indicates the type or category of language used in a devotional or religious context.
-
E.
devotionalSpread
Indicates the dissemination or expansion of devotional practices, beliefs, or sentiments from one source to other individuals, groups, or regions.
- F. None of above. chosen
Provenance (4 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afae2aa081909a59a8cd4f1d04e1 |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.