Triple
T34015715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramat Beit Shemesh Bet |
E872236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Haredi neighborhood |
C50690
|
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: Haredi neighborhood Context triple: [Ramat Beit Shemesh Bet, instanceOf, Haredi neighborhood]
-
A.
Haredi city
chosen
A Haredi city is an urban community in which the majority of residents are Haredi (ultra-Orthodox) Jews, characterized by strict religious observance, modest dress codes, gender-segregated public spaces, and institutions structured around Torah study and halachic (Jewish legal) norms.
-
B.
Jerusalem neighborhood
A Jerusalem neighborhood is a distinct urban area within the city of Jerusalem characterized by its unique historical, cultural, religious, and architectural identity, as well as its local community and services.
-
C.
Palestinian neighborhood
A Palestinian neighborhood is a localized residential area predominantly inhabited by Palestinians, characterized by shared cultural, social, and historical ties, as well as common community institutions and spaces.
-
D.
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.
-
E.
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.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:51 a.m.