Triple
T29972416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panteón de Reyes |
E761354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanesque art site |
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 art site Context triple: [Panteón de Reyes, instanceOf, Romanesque art site]
-
A.
Romanesque civic building
A Romanesque civic building is a public or governmental structure characterized by thick masonry walls, rounded arches, sturdy piers, small windows, and a fortress-like, monumental appearance typical of Romanesque architecture.
-
B.
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.
-
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.
medieval monastic site
A medieval monastic site is a religious complex, typically enclosed and self-sufficient, where monks or nuns lived, worshipped, worked, and followed a regulated spiritual routine during the Middle Ages.
-
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.
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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:32 p.m.