Triple
T22361936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahavat Olam |
E552798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish liturgical blessing |
C5355
|
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: Jewish liturgical blessing Context triple: [Ahavat Olam, instanceOf, Jewish liturgical blessing]
-
A.
Jewish prayer
chosen
Jewish prayer is a structured and heartfelt practice of communicating with God through traditional liturgy, blessings, and personal supplication, often performed in Hebrew and guided by daily, Sabbath, and holiday rhythms.
-
B.
Jewish liturgical corpus
The Jewish liturgical corpus is the body of prayers, blessings, poems, and scriptural readings developed across Jewish history and communities for use in communal and private worship throughout the religious calendar and life-cycle events.
-
C.
Jewish ritual object
A Jewish ritual object is a physical item used in Jewish religious practice or observance, often imbued with symbolic meaning and governed by specific laws and traditions.
-
D.
Yemenite Jewish liturgical tradition
The Yemenite Jewish liturgical tradition is a distinctive, meticulously preserved rite of prayer, chant, and scriptural recitation that reflects ancient Near Eastern Jewish practices, precise Hebrew pronunciation, and unique musical and textual customs developed within the Jewish communities of Yemen.
-
E.
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.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:44 p.m.