Triple
T26135530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo-Vaishnavite movement in Assam |
E659370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vaishnavite movement |
C19071
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Vaishnavite movement Context triple: [Neo-Vaishnavite movement in Assam, instanceOf, Vaishnavite movement]
-
A.
Hindu devotional movement
chosen
A Hindu devotional movement is a religious and social current centered on personal devotion (bhakti) to a chosen deity, expressed through practices like chanting, singing, ritual worship, and communal gatherings that shape followers’ beliefs, identities, and ways of life.
-
B.
Gaudiya Vaishnava
A Gaudiya Vaishnava is a follower of the devotional Hindu tradition centered on Sri Chaitanya Mahaprabhu, emphasizing loving devotion (bhakti) to Radha-Krishna as the Supreme Reality.
-
C.
Sri Vaishnava subsect
A Sri Vaishnava subsect is a distinct traditional community within the broader Sri Vaishnavism movement, defined by its specific theological interpretations, ritual practices, and lineage of spiritual teachers devoted to Vishnu and his incarnations.
-
D.
Vaishnavite ritual
Vaishnavite ritual is a structured set of devotional practices—such as chanting, offerings, and temple worship—performed to honor and seek the grace of Vishnu and his avatars.
-
E.
Shaivite tradition
The Shaivite tradition is a major Hindu devotional and philosophical stream centered on the worship of Shiva as the supreme reality, encompassing diverse rituals, yogic practices, temple cultures, and theological schools across South Asia.
- F. None of above.
Provenance (1 batch)
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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 8:17 p.m.