Triple
T18477500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pururavas |
E451470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary figure in Hindu mythology |
C17759
|
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: legendary figure in Hindu mythology Context triple: [Pururavas, instanceOf, legendary figure in Hindu mythology]
-
A.
figure in Hindu tradition
chosen
A figure in Hindu tradition is an individual—divine, semi-divine, mythological, or historical—who appears in Hindu scriptures, stories, or practices and embodies particular spiritual, moral, or cultural ideals.
-
B.
Character in the Ramayana
A Character in the Ramayana is an individual—divine, human, or demonic—whose actions, relationships, and moral choices drive the epic’s narrative and embody its spiritual and ethical teachings.
-
C.
Hindu legendary couple
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.
-
D.
symbol in Hinduism
A symbol in Hinduism is a visual, auditory, or ritual sign (such as the Om syllable, lotus, or trident) that embodies and communicates deeper spiritual, philosophical, or mythological meanings within the Hindu tradition.
-
E.
Buddhist legend
A Buddhist legend is a traditional narrative within Buddhism that conveys spiritual teachings, moral lessons, or the exemplary deeds of enlightened beings and revered figures.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:35 a.m.