Triple
T30490814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carvajal family of New Spain |
E775858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crypto-Jewish lineage |
C42518
|
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: crypto-Jewish lineage Context triple: [Carvajal family of New Spain, instanceOf, crypto-Jewish lineage]
-
A.
crypto-Jewish community
chosen
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.
-
B.
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.
-
C.
Jewish leadership dynasty
A Jewish leadership dynasty is a multigenerational lineage in which religious, communal, or intellectual authority is passed down within a Jewish family, shaping the spiritual and social life of their community over time.
-
D.
Jewish identity framework
A Jewish identity framework is a conceptual model that organizes the religious, cultural, ethnic, historical, and personal dimensions through which individuals and communities understand, express, and negotiate being Jewish.
-
E.
Ashkenazi Jewish subgroup
A subgroup of Ashkenazi Jews defined by shared geographic origins, cultural practices, religious traditions, and/or genetic lineages within the broader Ashkenazi Jewish population.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:13 p.m.