Triple
T22155696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boas family |
E547532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German-American Jewish family |
C18035
|
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: German-American Jewish family Context triple: [Boas family, instanceOf, German-American Jewish family]
-
A.
German-Jewish family
chosen
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.
-
B.
Polish-Jewish family
A Polish-Jewish family is a kinship group rooted in both Polish national culture and Jewish religious-ethnic heritage, often shaped by the historical experiences of Jewish life in Poland.
-
C.
Jewish scholarly family
A Jewish scholarly family is a multigenerational household or lineage devoted to the study, teaching, and transmission of Jewish religious texts, traditions, and intellectual pursuits.
-
D.
German family
A German family is a social unit typically consisting of parents and children living in Germany, shaped by German cultural norms, language, traditions, and legal frameworks around kinship and household life.
-
E.
Zionist family
A Zionist family is a household whose members share and actively support the Jewish national movement for the establishment, development, and security of a Jewish homeland in the Land of Israel, often integrating Zionist values into their cultural, religious, and educational life.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:33 p.m.