Triple
T30624934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saryati |
E779547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | person 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: person in Hindu mythology Context triple: [Saryati, instanceOf, person 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.
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.
-
C.
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.
-
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.
celestial object in Hindu mythology
A celestial object in Hindu mythology is a divine or cosmic body—such as a star, planet, constellation, or luminous weapon—endowed with spiritual significance, mythic narratives, and influence over cosmic order and human destiny.
- 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.