Triple
T34504223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Jimutavahana |
E885838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in Hindu tradition |
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: character in Hindu tradition Context triple: [Lord Jimutavahana, instanceOf, character in Hindu tradition]
-
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.
place in Hindu tradition
A place in Hindu tradition is a physical or sacred location—such as a temple, pilgrimage site, river, mountain, or city—imbued with religious, mythological, or spiritual significance and associated rituals.
-
C.
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.
-
D.
concept in Hinduism
A concept in Hinduism is an abstract idea, principle, or belief—such as dharma, karma, or moksha—that helps explain the nature of reality, ethical conduct, and the spiritual path within the Hindu tradition.
-
E.
episode in Hindu mythology
An episode in Hindu mythology is a distinct narrative unit—such as a story, incident, or event—within the larger mythic tradition that illustrates moral, philosophical, or cosmological themes through the actions of divine, heroic, or supernatural 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.