Triple
T29048902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domus Municipalis |
E735209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanesque civic building |
C54634
|
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 civic building Context triple: [Domus Municipalis, instanceOf, Romanesque civic building]
-
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.
Romanesque Revival building
A Romanesque Revival building is a structure designed in a 19th-century historicist style that reinterprets medieval Romanesque architecture through features like round arches, heavy masonry, robust towers, and deeply recessed openings.
-
C.
Manueline architectural monument
A Manueline architectural monument is a grand structure exemplifying the ornate, late-Gothic Portuguese style characterized by intricate maritime, religious, and royal symbolism carved into stone.
-
D.
Renaissance building
A Renaissance building is a structure characterized by symmetry, proportion, and classical elements such as columns, pilasters, arches, and domes, reflecting the revival of ancient Greek and Roman architectural principles during the 14th–17th centuries.
-
E.
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.
- F. None of above. chosen
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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:07 a.m.