Triple
T19977433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Jewish community core |
E493728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish community hub |
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 hub Context triple: [Houston Jewish community core, instanceOf, Jewish community hub]
-
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.
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 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.
-
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.
Yiddish cultural institution network
A Yiddish cultural institution network is a coordinated system of organizations, archives, educational centers, and community groups that collaborate to preserve, promote, and develop Yiddish language and culture across regions and generations.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:27 p.m.