Triple
T4515782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gita Jayanti celebrations |
E102149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu religious observance |
C14285
|
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: Hindu religious observance Context triple: [Gita Jayanti celebrations, instanceOf, Hindu religious observance]
-
A.
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.
-
B.
observance in India
chosen
Observance in India refers to the diverse religious, cultural, and social practices, rituals, and commemorations that people follow to honor traditions, deities, festivals, and significant life events across the country’s many communities.
-
C.
Jewish observance
Jewish observance is the practice of religious commandments, rituals, customs, and ethical principles rooted in Jewish law and tradition, guiding daily life, worship, and communal identity.
-
D.
Christian religious observance
Christian religious observance is the practice of worship, rituals, and disciplines—such as prayer, sacraments, and holy days—through which Christians express devotion to God and live out their faith in community and daily life.
-
E.
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.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:02 p.m.