Triple

T18712613
Position Surface form Disambiguated ID Type / Status
Subject Yiddish culture E457555 entity
Predicate instanceOf P0 FINISHED
Object Ashkenazi culture C20162 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: Ashkenazi culture
Context triple: [Yiddish culture, instanceOf, Ashkenazi culture]
  • A. 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.
  • 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. Ashkenazi Jewish subgroup chosen
    A subgroup of Ashkenazi Jews defined by shared geographic origins, cultural practices, religious traditions, and/or genetic lineages within the broader Ashkenazi Jewish population.
  • D. Haredi Jew
    A Haredi Jew is a member of a stream of Orthodox Judaism characterized by strict adherence to Jewish law, distinctive modest dress, and a strong emphasis on traditional religious study and community separation from secular society.
  • E. Sephardic Jew
    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.
  • 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_69d8d392aad081909fe31aa03e6e97d1 completed April 10, 2026, 10:40 a.m.
Created at: April 10, 2026, 11:50 a.m.