Triple
T35772349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerta de la Pellejería |
E1034197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance portal |
C62636
|
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: Renaissance portal Context triple: [Puerta de la Pellejería, instanceOf, Renaissance portal]
-
A.
Renaissance mass
A Renaissance mass is a large-scale, multi-movement sacred musical setting of the Catholic liturgy, typically for voices, characterized by imitative polyphony and based on techniques such as cantus firmus, parody, or paraphrase.
-
B.
Renaissance private library
A Renaissance private library is an exclusive, often lavishly decorated collection of books and manuscripts owned by a wealthy individual or family, serving as both a symbol of status and a center for humanist study and intellectual pursuits.
-
C.
Renaissance ramp
A Renaissance ramp is an elegantly engineered inclined passageway, often integrated into grand architectural designs of the Renaissance period, used to facilitate smooth movement of people, goods, or vehicles between different levels.
-
D.
Renaissance institution
A Renaissance institution is an organized social, political, religious, or educational body that structured and regulated public and intellectual life during the European Renaissance, fostering the revival of classical learning and arts.
-
E.
Renaissance square
A Renaissance square is a public urban space characterized by harmonious proportions, classical architectural elements, and a central role in civic, commercial, and cultural life during the Renaissance period.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.