Triple
T23820602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pieve di San Giovanni Battista a Galatrona |
E589226
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanesque parish church |
C13234
|
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: Romanesque parish church Context triple: [Pieve di San Giovanni Battista a Galatrona, instanceOf, Romanesque parish church]
-
A.
Romanesque church building
chosen
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.
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.
-
C.
Historic church
A historic church is a long-standing religious building of significant architectural, cultural, and spiritual importance that reflects the beliefs, artistry, and community life of its era.
-
D.
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.
-
E.
Gothic Revival church
A Gothic Revival church is a Christian worship building designed in the 19th-century revival of medieval Gothic architecture, featuring pointed arches, ribbed vaults, and ornate tracery.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 7:59 p.m.