Triple
T36849967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balumain |
E910649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | central deity in the Kalash religion |
C64741
|
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: central deity in the Kalash religion Context triple: [Balumain, instanceOf, central deity in the Kalash religion]
-
A.
Turkic deity
A Turkic deity is a divine being from the mythologies of Turkic peoples, embodying natural forces, social values, or cosmic principles within their traditional belief systems.
-
B.
Hindu folk deity
A Hindu folk deity is a locally revered divine figure, often rooted in regional legends and ancestral or nature worship, who embodies community-specific beliefs and practices outside or alongside mainstream Hindu pantheons.
-
C.
traditional Bodo deity
A traditional Bodo deity is a supernatural being revered in Bodo indigenous religion, embodying natural forces, ancestral spirits, and cultural values through localized rituals and festivals.
-
D.
Mongolic deity
A Mongolic deity is a supernatural being revered in Mongolic religious traditions, often associated with natural forces, ancestral spirits, or protective roles within nomadic life.
-
E.
Vaishnava deity associate
A Vaishnava deity associate is a divine or semi-divine figure closely connected to a principal Vishnu or Krishna form, serving as companion, consort, attendant, or empowered servant within Vaishnava theology and worship.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.