Triple
T24282317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eid al-Ghadir |
E605578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shia religious holiday |
C5364
|
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: Shia religious holiday Context triple: [Eid al-Ghadir, instanceOf, Shia religious holiday]
-
A.
Islamic religious festival
An Islamic religious festival is a recurring sacred occasion in Islam, marked by specific rituals, communal worship, and cultural practices that commemorate key events in Islamic belief and history.
-
B.
Islamic religious event
chosen
An Islamic religious event is a scheduled gathering or observance rooted in Islamic beliefs and practices, such as prayers, festivals, commemorations, or educational activities, conducted according to Islamic teachings and traditions.
-
C.
Jewish holiday
A Jewish holiday is a recurring religious and cultural observance in Judaism, marked by specific rituals, prayers, and traditions that commemorate historical events, spiritual themes, or agricultural cycles.
-
D.
Sikh religious festival
A Sikh religious festival is a communal celebration that commemorates significant events in Sikh history and spirituality through prayer, scripture recitation, kirtan (devotional singing), and shared meals (langar) at gurdwaras and in the wider community.
-
E.
Iranian festival
An Iranian festival is a culturally significant celebration in Iran, often rooted in ancient Persian traditions, that marks seasonal changes, religious events, or national commemorations through rituals, gatherings, food, music, and symbolic customs.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:08 a.m.