Triple
T19850559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kahana |
E476980
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ashkenazi surname |
C37838
|
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 surname Context triple: [Kahana, instanceOf, Ashkenazi surname]
-
A.
Hebrew-language surname
A Hebrew-language surname is a family name derived from or adapted into the Hebrew language, often reflecting Hebrew words, biblical names, places, or cultural-historical origins within Jewish communities.
-
B.
Yiddish-language surname
chosen
A Yiddish-language surname is a family name derived from the Yiddish language, often reflecting ancestral occupations, places of origin, personal traits, or patronymic forms within Ashkenazi Jewish communities.
-
C.
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.
-
D.
Eastern European surname
An Eastern European surname is a family name originating from countries in Eastern Europe, often reflecting linguistic, geographic, occupational, or patronymic traditions specific to the region.
-
E.
Yiddish given name
A Yiddish given name is a personal name traditionally used by Ashkenazi Jews, typically derived from the Yiddish language and reflecting Jewish religious, cultural, or linguistic heritage.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:51 p.m.