Triple
T15801148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairo Geniza fragments |
E383100
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish manuscripts |
C2085
|
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 manuscripts Context triple: [Cairo Geniza fragments, instanceOf, Jewish manuscripts]
-
A.
medieval Hebrew manuscript
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.
-
B.
Tosefta manuscript
A Tosefta manuscript is a handwritten document preserving the text of the Tosefta, an early rabbinic compilation of legal traditions that supplements and parallels the Mishnah.
-
C.
ancient manuscripts
chosen
Ancient manuscripts are original handwritten documents from past civilizations, typically preserved on materials like papyrus, parchment, or early paper, that provide primary evidence of historical, religious, literary, or scientific thought.
-
D.
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.
-
E.
Jewish studies library
A Jewish studies library is a specialized collection of books, manuscripts, and digital resources focused on Jewish history, religion, culture, languages, and thought, curated to support research, education, and community learning.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:48 a.m.