Triple
T6454330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lithuanian Jewry |
E139954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical Jewish community |
C14738
|
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: historical Jewish community Context triple: [Lithuanian Jewry, instanceOf, historical Jewish community]
-
A.
historic Jewish quarter
chosen
A historic Jewish quarter is an urban district where Jewish communities historically lived, worked, and worshipped, characterized by synagogues, cultural institutions, distinctive architecture, and remnants of religious and communal life.
-
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.
Sephardic Jewish culture
Sephardic Jewish culture encompasses the religious traditions, languages, music, cuisine, and social customs developed by Jews of Iberian, North African, and Middle Eastern origin, shaped by centuries of migration, coexistence, and adaptation.
-
E.
Jewish historical work
A Jewish historical work is a text that records, interprets, and reflects on the experiences, events, and developments of Jewish people and communities across time, often integrating religious, cultural, and social perspectives.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:48 p.m.