Triple
T31201687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marranos |
E795492
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iberian Jews |
C6400
|
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: Iberian Jews Context triple: [Marranos, instanceOf, Iberian Jews]
-
A.
Sephardic Jew
chosen
A Sephardic Jew is a Jewish person whose ancestry traces primarily to the Iberian Peninsula (Spain and Portugal) and the communities that emerged after their expulsion, often characterized by distinct religious customs, liturgy, and cultural traditions.
-
B.
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.
-
C.
converso family
A converso family is a household of Jews in medieval or early modern Iberia who converted to Christianity—often under pressure—while frequently maintaining elements of Jewish identity or practice in secret.
-
D.
Ashkenazic Jew
An Ashkenazic Jew is a Jewish person whose ancestry traces primarily to the Jewish communities of Central and Eastern Europe, historically characterized by distinct religious customs, Yiddish language, and cultural traditions.
-
E.
Georgian Jews
Georgian Jews are a distinct Jewish ethnocultural group originating from the country of Georgia, characterized by their ancient presence in the region, unique Georgian-Jewish traditions, and use of both Georgian and Hebrew languages.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:09 p.m.