Triple
T22468995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parushni River |
E555438
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vedic geographic entity |
C15062
|
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: Vedic geographic entity Context triple: [Parushni River, instanceOf, Vedic geographic entity]
-
A.
Vedic hydronym
chosen
A Vedic hydronym is a proper name of a river, stream, or other water body attested in the Vedic texts of ancient India, often carrying religious, mythological, or geographical significance.
-
B.
historical geographic entity
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
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.
Krishna-related sacred geography
Krishna-related sacred geography encompasses the network of places, landscapes, and pilgrimage sites associated with the life, legends, and worship of Krishna, understood as spiritually charged spaces that embody and reenact his divine presence and pastimes.
-
E.
Hindu lunar mansion
A Hindu lunar mansion is one of the 27 (sometimes 28) divisions of the ecliptic, called nakshatras, used in Vedic astrology to track the Moon’s daily position and interpret its influence on human life and events.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:48 p.m.