Triple
T17556425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castelvecchio (Buonconsiglio Castle) |
E427601
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic building complex section |
C29736
|
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: historic building complex section Context triple: [Castelvecchio (Buonconsiglio Castle), instanceOf, historic building complex section]
-
A.
historic building section
chosen
A historic building section is a vertical cut-through representation of an older, culturally or architecturally significant structure that reveals its internal organization, construction methods, and spatial relationships over time.
-
B.
ancient building complex
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
-
C.
historic architecture
Historic architecture encompasses buildings and structures from past eras that embody the cultural, technological, and artistic values of the time in which they were created.
-
D.
ancient building
An ancient building is a historically significant structure from antiquity, often characterized by enduring construction materials, distinctive architectural styles, and cultural or archaeological importance.
-
E.
monumental complex
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.