Triple
T19860447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congregation Shaar Hashomayim |
E477241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Orthodox Jewish congregation |
C42423
|
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: Orthodox Jewish congregation Context triple: [Congregation Shaar Hashomayim, instanceOf, Orthodox Jewish congregation]
-
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.
Jewish communal organization
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.
-
C.
Haredi Jew
A Haredi Jew is a member of a stream of Orthodox Judaism characterized by strict adherence to Jewish law, distinctive modest dress, and a strong emphasis on traditional religious study and community separation from secular society.
-
D.
Protestant congregation
A Protestant congregation is a local community of believers who gather regularly for worship, teaching, fellowship, and service in accordance with Protestant Christian doctrines and practices.
-
E.
Jewish mystical community
A Jewish mystical community is a group of individuals who gather to study, practice, and embody Jewish esoteric traditions—such as Kabbalah and Hasidic spirituality—through shared rituals, texts, and contemplative practices.
- F. None of above. chosen
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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:51 p.m.