Triple
T19067813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of St. Clement and St. Panteleimon at Plaošnik |
E466712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconstructed medieval church |
C32941
|
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: reconstructed medieval church Context triple: [Church of St. Clement and St. Panteleimon at Plaošnik, instanceOf, reconstructed medieval church]
-
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.
reconstructed church
chosen
A reconstructed church is a religious building that has been rebuilt or extensively restored to replicate its original historical form, structure, and appearance after damage, destruction, or significant alteration.
-
C.
Romanesque-Byzantine church
A Romanesque-Byzantine church is a religious building that combines the heavy, rounded-arch masonry and fortress-like massing of Romanesque architecture with the domes, mosaics, and centralized plans characteristic of Byzantine design.
-
D.
neo-Romanesque church
A neo-Romanesque church is a religious building designed in a 19th- or early 20th-century revival of Romanesque architecture, featuring rounded arches, thick walls, sturdy piers, and often simple, massive forms.
-
E.
fortified church
A fortified church is a religious building designed or modified with defensive features—such as walls, towers, and battlements—to protect its congregation and surrounding community during times of conflict.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:03 p.m.