Triple
T16680746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radak |
E405331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Jewish biblical commentator |
C14171
|
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 Jewish biblical commentator Context triple: [Radak, instanceOf, medieval Jewish biblical commentator]
-
A.
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.
-
B.
Jewish exegete
chosen
A Jewish exegete is a scholar who interprets and explains Jewish sacred texts, especially the Hebrew Bible, using linguistic, historical, and theological analysis.
-
C.
medieval Jewish philosopher
A medieval Jewish philosopher is a thinker from roughly the 9th to 15th centuries who engaged with Jewish religious tradition and texts using the philosophical methods and ideas of their time, often integrating Jewish theology with Greco-Arabic and scholastic thought.
-
D.
Jewish biblical commentary
Jewish biblical commentary is a tradition of interpretive writings that explain, analyze, and expand upon the Hebrew Bible’s text, language, and meaning from religious, legal, ethical, and historical perspectives.
-
E.
Jewish grammarian
A Jewish grammarian is a scholar who studies, analyzes, and explains the structure, rules, and usage of Hebrew and other Jewish languages within their historical, religious, and literary contexts.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.