Triple
T17937400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parjanya |
E448501
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | person in Hindu tradition |
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 tradition Context triple: [Parjanya, instanceOf, person in Hindu tradition]
-
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.
denomination of Hinduism
A denomination of Hinduism is a distinct religious tradition within Hinduism characterized by its own set of core deities, philosophies, rituals, and community practices while still sharing the broader Hindu cultural and scriptural framework.
-
C.
Hindu denomination
A Hindu denomination is a distinct religious tradition within Hinduism characterized by shared beliefs, practices, scriptures, and devotional focus, often centered on a particular deity or philosophical school.
-
D.
Hindu social category
A Hindu social category is a classification within Hindu society that groups individuals based on shared religious, cultural, ritual, or status-related characteristics, such as caste, sect, or community.
-
E.
symbol in Hinduism
A symbol in Hinduism is a visual, auditory, or ritual sign (such as the Om syllable, lotus, or trident) that embodies and communicates deeper spiritual, philosophical, or mythological meanings within the Hindu tradition.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.