Triple
T8606268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shomrim neighborhood watch |
E203805
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish community organization |
C9468
|
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 community organization Context triple: [Shomrim neighborhood watch, instanceOf, Jewish community organization]
-
A.
Jewish communal organization
chosen
A Jewish communal organization is a structured group that provides religious, cultural, educational, and social services to support and strengthen Jewish life and identity within a specific community.
-
B.
Jewish activist movement
A Jewish activist movement is a collective effort by Jewish individuals and communities to pursue social, political, or cultural change grounded in Jewish values, history, and identity.
-
C.
Zionist organization
A Zionist organization is a group dedicated to supporting, promoting, or advancing the political, cultural, or social goals associated with Zionism, particularly the establishment, security, and development of a Jewish homeland in Israel.
-
D.
rabbinical association
A rabbinical association is an organized body of rabbis that provides professional support, sets ethical and religious standards, and represents its members within the broader Jewish and civic communities.
-
E.
Indian diaspora organization
An Indian diaspora organization is a group formed by people of Indian origin living outside India to promote cultural heritage, provide community support, and foster social, economic, and professional connections with both their host country and India.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:25 p.m.