Triple
T26026907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merhav Am |
E647317
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious Jewish community |
C35084
|
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: religious Jewish community Context triple: [Merhav Am, instanceOf, religious Jewish community]
-
A.
Orthodox Jewish community
chosen
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.
Orthodox Jewish congregation
An Orthodox Jewish congregation is a community of Jews who gather regularly to pray, study Torah, and observe Jewish law and tradition in accordance with Orthodox halachic standards.
-
C.
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.
-
D.
Sephardic Jewish congregation
A Sephardic Jewish congregation is a community of Jews of Iberian, North African, and Middle Eastern descent who gather for worship, study, and communal life following Sephardic liturgy, customs, and traditions.
-
E.
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.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:05 a.m.