Triple
T33879984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish community of Nevis |
E868457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic Jewish community |
C54781
|
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: historic Jewish community Context triple: [Jewish community of Nevis, instanceOf, historic Jewish community]
-
A.
historic Jewish quarter
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 history
Jewish history is the study of the experiences, cultures, beliefs, and transformations of Jewish people and communities from ancient times to the present across diverse regions of the world.
-
C.
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.
-
D.
historical religious community
chosen
A historical religious community is a group of people in a specific past time and place who shared common religious beliefs, practices, institutions, and identities that shaped their social and cultural life.
-
E.
crypto-Jewish community
A crypto-Jewish community is a group of people who secretly maintain Jewish beliefs and practices while outwardly conforming to another dominant religion or culture, often due to historical persecution or social pressure.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.