Triple
T13451304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sefer HaChaim |
E320612
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish liturgical concept |
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: Jewish liturgical concept Context triple: [Sefer HaChaim, instanceOf, Jewish liturgical concept]
-
A.
figure in Jewish tradition
A figure in Jewish tradition is an individual—historical, legendary, or symbolic—who plays a significant role in Jewish religious texts, narratives, law, or cultural memory.
-
B.
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.
-
C.
component of Judaism
A component of Judaism is a fundamental element—such as belief, practice, text, institution, or cultural tradition—that collectively shapes and expresses Jewish religious life and identity.
-
D.
Jewish theological doctrine
Jewish theological doctrine is the body of religious beliefs and interpretations within Judaism concerning God, creation, covenant, law, and the relationship between the divine and the Jewish people.
-
E.
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.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:41 p.m.