Triple
T30624964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabhanedishta |
E779548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | person in Hindu scripture |
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: person in Hindu scripture Context triple: [Nabhanedishta, instanceOf, person in Hindu scripture]
-
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.
Hindu religious texts
Hindu religious texts are a diverse body of ancient and medieval scriptures—including the Vedas, Upanishads, epics like the Mahabharata and Ramayana, and numerous Puranas and devotional works—that articulate Hindu philosophy, mythology, rituals, and ethical teachings.
-
C.
Hindu technical scripture
A Hindu technical scripture is a specialized sacred text that systematically presents practical knowledge—such as ritual procedures, architecture, arts, sciences, or governance—within a Hindu religious and philosophical framework.
-
D.
Varkari scripture
Varkari scripture refers to the devotional texts, abhangas, and hagiographies central to the Varkari tradition of Maharashtra, guiding personal devotion to Vithoba through teachings on bhakti, morality, and egalitarian spirituality.
-
E.
entity in Indian epic tradition
An entity in the Indian epic tradition is any person, creature, deity, or supernatural being that participates in the narrative, cosmology, or moral framework of epics like the Mahābhārata and Rāmāyaṇa.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:27 p.m.