Triple
T22850347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nata Sankirtana |
E566339
|
entity |
| Predicate | devotionalTo |
P21326
|
FINISHED |
| Object | Hindu deities |
—
|
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: Hindu deities | Statement: [Nata Sankirtana, devotionalTo, Hindu deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalTo Context triple: [Nata Sankirtana, devotionalTo, Hindu deities]
-
A.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
B.
devotionalCollection
Indicates that one entity is a curated set or compilation of devotional items, works, or practices associated with another entity.
-
C.
devotionalObject
Indicates that one entity is used by or associated with another as an object of religious or spiritual devotion.
-
D.
devotionalImportance
Indicates the degree to which something is regarded as significant or central within acts of devotion, worship, or religious practice.
-
E.
associatedDevotion
chosen
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb74700819090d191b3a7a17034 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.