Triple
T19931629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurukula of Sandipani Muni |
E479067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | place in Hindu tradition |
C42728
|
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: place in Hindu tradition Context triple: [Gurukula of Sandipani Muni, instanceOf, place in Hindu tradition]
-
A.
figure in Hindu tradition
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.
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.
-
C.
Hindu cosmological realm
A Hindu cosmological realm is a metaphysical plane of existence within the layered universe of Hindu thought, inhabited by specific beings and governed by particular spiritual, moral, and karmic laws.
-
D.
place in Christian tradition
A place in Christian tradition is a spiritually or theologically significant location—earthly or heavenly—where key events of salvation history, worship, or divine presence are believed to occur or be especially manifest.
-
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. chosen
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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:53 p.m.