Triple
T30244520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ShUM cities |
E769019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Jewish communities |
C14738
|
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 communities Context triple: [ShUM cities, instanceOf, medieval Jewish communities]
-
A.
medieval Jewish intellectual current
A medieval Jewish intellectual current is a historically situated stream of thought, scholarship, and religious-philosophical interpretation that developed within Jewish communities, shaped by their engagement with surrounding cultures, texts, and theological debates.
-
B.
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.
-
C.
crypto-Jewish community
A crypto-Jewish community is a group of people who secretly maintain Jewish beliefs and practices while outwardly conforming to another dominant religion or culture, often due to historical persecution or social pressure.
-
D.
historic Jewish quarter
chosen
A historic Jewish quarter is an urban district where Jewish communities historically lived, worked, and worshipped, characterized by synagogues, cultural institutions, distinctive architecture, and remnants of religious and communal life.
-
E.
Sephardic Jewish culture
Sephardic Jewish culture encompasses the religious traditions, languages, music, cuisine, and social customs developed by Jews of Iberian, North African, and Middle Eastern origin, shaped by centuries of migration, coexistence, and adaptation.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:39 p.m.