Triple
T9589006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gates of Prayer |
E231368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Reform Jewish liturgical text |
C16573
|
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: Reform Jewish liturgical text Context triple: [Gates of Prayer, instanceOf, Reform Jewish liturgical text]
-
A.
Jewish liturgical corpus
chosen
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.
-
B.
rabbinic literature
Rabbinic literature is the body of Jewish religious writings produced by rabbinic sages, including the Mishnah, Talmud, Midrash, and related commentaries, that interpret and expand upon the Hebrew Bible and Jewish law.
-
C.
rabbinic text
A rabbinic text is a work produced by Jewish sages that records their interpretations, legal rulings, narratives, and theological reflections on the Hebrew Bible and Jewish law.
-
D.
Jewish mystical text edition
A Jewish mystical text edition is a curated, scholarly presentation of one or more kabbalistic or other esoteric Jewish works, typically including a critical text, annotations, translations, and contextual commentary.
-
E.
Jewish prayer
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.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:06 p.m.