Triple
T20430199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of the Sign |
E501109
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Hebrew work |
C28376
|
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: medieval Hebrew work Context triple: [Book of the Sign, instanceOf, medieval Hebrew work]
-
A.
medieval Hebrew lexicographical work
A medieval Hebrew lexicographical work is a scholarly text from the Middle Ages that systematically defines, explains, and often translates Hebrew words, typically for biblical, liturgical, or grammatical study.
-
B.
medieval Hebrew manuscript
chosen
A medieval Hebrew manuscript is a handwritten document produced between the 9th and 15th centuries in Hebrew script, often containing religious, legal, philosophical, or literary texts and frequently adorned with distinctive marginalia, illuminations, and scribal annotations.
-
C.
Judeo-Arabic work
A Judeo-Arabic work is a text written in Arabic using Hebrew script, typically produced by Jewish communities in the medieval Islamic world for religious, philosophical, or everyday purposes.
-
D.
Lurianic Kabbalah text
A Lurianic Kabbalah text is a work that presents, explains, or elaborates on the mystical doctrines of Rabbi Isaac Luria, focusing on concepts such as tzimtzum (divine contraction), shevirat ha-kelim (shattering of the vessels), and tikkun (cosmic repair).
-
E.
medieval Jewish translator
A medieval Jewish translator is a scholar who rendered religious, philosophical, scientific, or literary works between Hebrew, Arabic, Latin, and vernacular languages, facilitating intellectual exchange across Jewish and broader medieval cultures.
- 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_69e0b4aa68fc8190b1a14c55575ef04a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:31 a.m.