Triple
T11068301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baladi rite |
E261680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yemenite Jewish liturgical tradition |
C29125
|
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: Yemenite Jewish liturgical tradition Context triple: [Baladi rite, instanceOf, Yemenite Jewish liturgical tradition]
-
A.
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.
-
B.
Sephardic Jewish culture
Sephardic Jewish culture encompasses the religious traditions, languages, music, cuisine, and social customs developed by Jews of Iberian, North African, and Middle Eastern origin, shaped by centuries of migration, coexistence, and adaptation.
-
C.
Hebrew religious work
A Hebrew religious work is a text composed primarily in Hebrew that expresses, interprets, or transmits Jewish religious beliefs, laws, rituals, ethics, or spiritual teachings.
-
D.
Lurianic Kabbalistic doctrine
A mystical Jewish theological framework developed by Rabbi Isaac Luria that explains creation, divine contraction (tzimtzum), cosmic shattering (shevirat ha-kelim), and the human role in restoring harmony to the universe through spiritual repair (tikkun).
-
E.
Hebrew cantillation marks
Hebrew cantillation marks are a system of symbols added to biblical texts that indicate melodic chanting patterns, syntactic breaks, and accentuation for liturgical reading.
- F. None of above. chosen
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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:26 p.m.