Triple
T3912898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gimpel the Fool |
E87364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yiddish-language literary work |
C13537
|
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: Yiddish-language literary work Context triple: [Gimpel the Fool, instanceOf, Yiddish-language literary work]
-
A.
Yiddish-language work
chosen
A Yiddish-language work is any creative, scholarly, or informational piece—such as literature, theater, film, music, or academic writing—produced primarily in the Yiddish language.
-
B.
Yiddish-language writer
A Yiddish-language writer is an author who primarily composes literary, journalistic, or scholarly works in the Yiddish language, contributing to its cultural, historical, and linguistic tradition.
-
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.
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.
-
E.
Old Gutnish literature
Old Gutnish literature comprises the body of medieval texts written in the Old Gutnish language of Gotland, including legal codes, religious writings, and poetic works that reflect the island’s distinct linguistic and cultural heritage within the broader Old Norse tradition.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.