Triple
T20353026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Indra |
E496065
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | place in Hindu mythology |
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 mythology Context triple: [City of Indra, instanceOf, place in Hindu mythology]
-
A.
place in Hindu tradition
chosen
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.
-
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.
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.
-
D.
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.
-
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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:25 a.m.