Triple
T31358188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radha Gopinath |
E799793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu deity pair |
C17092
|
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: Hindu deity pair Context triple: [Radha Gopinath, instanceOf, Hindu deity pair]
-
A.
Hindu legendary couple
chosen
A Hindu legendary couple is a pair of figures from Hindu mythology or epic tradition whose relationship embodies idealized virtues such as devotion, dharma, love, and sacrifice, often serving as moral and spiritual exemplars.
-
B.
associate of Radha and Krishna
An associate of Radha and Krishna is a devoted companion who participates in, facilitates, and relishes the divine pastimes and loving exchanges of Radha and Krishna in the spiritual realm.
-
C.
consort of Vishnu
The consort of Vishnu is the divine partner, most prominently the goddess Lakshmi, who embodies prosperity, compassion, and cosmic balance while accompanying Vishnu in sustaining and preserving the universe.
-
D.
Hindu mythological group
A Hindu mythological group is a collection of deities, sages, demons, or legendary beings that appear together within Hindu mythology, often sharing a common origin, function, or narrative role.
-
E.
Vaishnava deity associate
A Vaishnava deity associate is a divine or semi-divine figure closely connected to a principal Vishnu or Krishna form, serving as companion, consort, attendant, or empowered servant within Vaishnava theology and worship.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:17 p.m.