Triple
T17738803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sopron Synagogue |
E442795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval synagogue |
C3963
|
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 synagogue Context triple: [Sopron Synagogue, instanceOf, medieval synagogue]
-
A.
medieval church
A medieval church is a religious building from the Middle Ages, typically characterized by stone construction, vaulted ceilings, stained glass windows, and architectural styles such as Romanesque or Gothic, serving as a center for worship and community life.
-
B.
Jewish temple
chosen
A Jewish temple is a sacred place of worship, communal gathering, and religious practice for Jews, serving as a center for prayer, study, and cultural life.
-
C.
medieval baptistery
A medieval baptistery is a separate, often centrally planned religious building or chapel, typically adjacent to a church or cathedral, designed specifically for administering the sacrament of baptism and richly adorned with symbolic art and architecture.
-
D.
Hieronymite monastery
A Hieronymite monastery is a religious complex belonging to the Order of Saint Jerome, characterized by its contemplative monastic life, dedication to scholarship and prayer, and often notable historical and architectural significance.
-
E.
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.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:09 a.m.