Triple
T7675407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashkenazi surnames |
E173849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish surnames |
C13336
|
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: Jewish surnames Context triple: [Ashkenazi surnames, instanceOf, Jewish surnames]
-
A.
Hebrew-language surname
chosen
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.
Kaifeng Jewish surname
A Kaifeng Jewish surname is a family name used by the historic Jewish community of Kaifeng, China, often reflecting sinicized forms of Hebrew or foreign names adapted into Chinese language and culture.
-
C.
Hebrew given name
A Hebrew given name is a personal first name derived from the Hebrew language and tradition, often rooted in biblical, religious, or culturally significant meanings.
-
D.
German-Jewish family
A German-Jewish family is a kinship group whose members share both German cultural or national ties and Jewish religious, ethnic, or cultural heritage, shaped by the historical experiences of Jews in German-speaking lands.
-
E.
Polish-language surname
A Polish-language surname is a family name originating from the Polish language, often reflecting ancestry, occupation, geography, or personal characteristics within Polish cultural and linguistic 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:01 p.m.