Triple
T24491769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish community of Los Angeles |
E617658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diaspora Jewish community |
C36509
|
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: diaspora Jewish community Context triple: [Jewish community of Los Angeles, instanceOf, diaspora Jewish community]
-
A.
Orthodox Jewish community
An Orthodox Jewish community is a group of Jews who live according to traditional Jewish law (Halakha), maintaining religious observance, communal institutions, and cultural practices rooted in longstanding rabbinic interpretation.
-
B.
crypto-Jewish community
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.
-
C.
diaspora organizations
Diaspora organizations are formal or informal groups formed by people living outside their country or region of origin to support mutual aid, cultural preservation, advocacy, and transnational connections with their homelands and host societies.
-
D.
Jewish settlement
A Jewish settlement is a community or residential area established and inhabited primarily by Jewish people, often reflecting specific historical, religious, or political contexts.
-
E.
Jewish diaspora region
chosen
A Jewish diaspora region is a geographic area outside the historical Land of Israel where Jewish communities have settled, developed distinct cultural, religious, and social practices, and maintained connections to broader Jewish identity and tradition.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:22 a.m.