Triple
T31696487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Movement for Reform Judaism |
E808931
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish denominational body |
C26812
|
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 denominational body Context triple: [Movement for Reform Judaism, instanceOf, Jewish denominational body]
-
A.
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.
-
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.
denominational body
chosen
A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
-
D.
Jewish religious movement
A Jewish religious movement is an organized stream within Judaism that shares distinctive beliefs, practices, and interpretations of Jewish law and tradition, shaping how its adherents understand and live out Jewish identity.
-
E.
Jewish political group
A Jewish political group is an organized body of individuals, primarily identifying as Jewish or focused on Jewish interests, that engages in political advocacy, policymaking, or representation related to Jewish communities, Israel, or broader social and civic issues.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:10 p.m.