Triple
T15062192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of the King |
E379655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine-Romanesque church |
C15656
|
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: Byzantine-Romanesque church Context triple: [Church of the King, instanceOf, Byzantine-Romanesque church]
-
A.
Romanesque church building
A Romanesque church building is a medieval Christian structure characterized by thick stone walls, rounded arches, sturdy piers, small windows, and a fortress-like, monumental appearance.
-
B.
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.
-
C.
Romanesque monastery
A Romanesque monastery is a medieval monastic complex characterized by massive stone construction, rounded arches, barrel or groin vaults, and a cloister-centered layout designed for communal religious life, prayer, and self-sufficiency.
-
D.
Baroque church
A Baroque church is a richly ornamented Christian worship building characterized by dramatic spatial compositions, dynamic forms, and lavish decorative elements designed to evoke emotional and spiritual awe.
-
E.
Neo-Byzantine building
chosen
A Neo-Byzantine building is a structure designed in a revival style that draws on medieval Byzantine architecture, featuring elements such as domes, rounded arches, rich ornamentation, and often elaborate brick or stonework.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:02 a.m.