Triple
T35858461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shem HaGedolim |
E1036573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish bibliographical work |
C35845
|
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 bibliographical work Context triple: [Shem HaGedolim, instanceOf, Jewish bibliographical work]
-
A.
Jewish historical work
A Jewish historical work is a text that records, interprets, and reflects on the experiences, events, and developments of Jewish people and communities across time, often integrating religious, cultural, and social perspectives.
-
B.
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.
-
C.
Jewish studies work
A Jewish studies work is a scholarly or educational text that explores aspects of Jewish history, religion, culture, thought, or practice, often using interdisciplinary methods and primary sources.
-
D.
Jewish studies reference
chosen
A Jewish studies reference is a scholarly resource—such as a dictionary, encyclopedia, bibliography, or handbook—that provides authoritative background information, definitions, and context on Jewish history, texts, traditions, and culture.
-
E.
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.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.