Triple
T14744664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakewood yeshiva community |
E346436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Orthodox 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: Orthodox Jewish community Context triple: [Lakewood yeshiva community, instanceOf, Orthodox Jewish community]
-
A.
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.
-
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.
Levantine community
A Levantine community is a social group rooted in the Eastern Mediterranean region (the Levant), characterized by shared historical, cultural, linguistic, and often religious ties that span modern national borders.
-
D.
Eastern Orthodox community
An Eastern Orthodox community is a group of faithful united in worship, doctrine, and sacramental life within the Eastern Orthodox Church, typically centered around a parish or local congregation and its clergy.
-
E.
Hasidic dynasty
A Hasidic dynasty is a spiritual and familial leadership line within Hasidic Judaism, typically centered around a revered rebbe whose teachings, customs, and authority are followed by a devoted community across generations.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:30 a.m.