Triple
T5762961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Carlo alle Quattro Fontane |
E127140
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage monument in Rome |
C18754
|
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: cultural heritage monument in Rome Context triple: [San Carlo alle Quattro Fontane, instanceOf, cultural heritage monument in Rome]
-
A.
ancient Roman monument
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
-
B.
palace in Vatican City
A palace in Vatican City is a grand, historically and architecturally significant residence or administrative complex within the sovereign territory of the Holy See, often serving religious, diplomatic, or governmental functions.
-
C.
national monument of Italy
A national monument of Italy is an officially recognized site, structure, or landscape of exceptional historical, cultural, or artistic significance that is protected and preserved by the Italian state.
-
D.
hill of Rome
A hill of Rome is one of the elevated landforms within the city that historically shaped its topography, urban development, and cultural identity.
-
E.
cultural heritage monument in Berlin
A cultural heritage monument in Berlin is a legally protected building, site, or structure recognized for its historical, architectural, or cultural significance within the city’s heritage conservation framework.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:49 p.m.