Triple
T38608383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish quarter of Besalú |
E934408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Jewish neighborhood |
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: medieval Jewish neighborhood Context triple: [Jewish quarter of Besalú, instanceOf, medieval Jewish neighborhood]
-
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.
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.
medieval urban district
A medieval urban district is a distinct, often walled or gated, neighborhood within a medieval town or city characterized by its specific social, economic, or administrative functions and spatial organization.
-
D.
Jewish ghetto inhabitant
A Jewish ghetto inhabitant is a Jewish person forcibly confined to a segregated, restricted urban district under discriminatory laws or occupation, typically facing overcrowding, deprivation, and persecution.
-
E.
Jewish heritage
Jewish heritage encompasses the religious traditions, cultural practices, historical experiences, and shared identity passed down through generations of the Jewish people.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.