Triple
T9361674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wissenschaftliche Zeitschrift für jüdische Theologie |
E225289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish studies journal |
C27096
|
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 studies journal Context triple: [Wissenschaftliche Zeitschrift für jüdische Theologie, instanceOf, Jewish studies journal]
-
A.
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.
-
B.
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.
-
C.
Jewish scholar
A Jewish scholar is an individual deeply engaged in the study, interpretation, and teaching of Jewish texts, traditions, law, and thought within their historical and cultural contexts.
-
D.
historian of Judaism
A historian of Judaism is a scholar who researches, analyzes, and interprets the historical development, texts, practices, and cultural contexts of Jewish people and religion across different periods and regions.
-
E.
Jewish history
Jewish history is the study of the experiences, cultures, beliefs, and transformations of Jewish people and communities from ancient times to the present across diverse regions of the world.
- 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:42 p.m.