Triple
T15796733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sepharad (Spain and Provence) |
E383002
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical Jewish cultural region |
C145
|
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: historical Jewish cultural region Context triple: [Sepharad (Spain and Provence), instanceOf, historical Jewish cultural region]
-
A.
region of ancient Palestine
A region of ancient Palestine is a geographically and culturally distinct area within the historical land of Palestine, defined by its political boundaries, settlements, and role in biblical and Near Eastern history.
-
B.
historic Jewish quarter
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.
-
C.
cultural region
chosen
A cultural region is a geographic area characterized by shared cultural traits such as language, religion, customs, and social norms that distinguish it from surrounding areas.
-
D.
historical region of Ukraine
A historical region of Ukraine is a geographically defined area within present-day Ukraine that is distinguished by its unique historical development, cultural heritage, and traditional boundaries formed over past centuries.
-
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.
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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:48 a.m.