Triple
T29776285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa di Pratolino |
E755387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance garden complex |
C12406
|
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 garden complex Context triple: [Villa di Pratolino, instanceOf, Renaissance garden complex]
-
A.
Renaissance palace
A Renaissance palace is a grand urban residence characterized by symmetrical facades, classical orders, and richly decorated interiors that reflect the humanist ideals and artistic innovations of the Renaissance period.
-
B.
palace and park ensemble
chosen
A palace and park ensemble is a unified architectural and landscape complex where a grand residence is integrated with designed gardens, water features, and surrounding grounds to form a cohesive cultural and aesthetic whole.
-
C.
Renaissance urban ensemble
A Renaissance urban ensemble is a cohesive grouping of buildings, streets, and public spaces that collectively embody the architectural, artistic, and spatial principles of the Renaissance period within a city.
-
D.
historic garden
A historic garden is a designed outdoor space of recognized cultural, aesthetic, or historical significance, preserved or restored to reflect the landscape styles, plantings, and features of a particular period or tradition.
-
E.
royal stables complex
A royal stables complex is an organized ensemble of buildings and yards designed to house, train, and maintain horses and related equipment for a royal household’s transportation, ceremonial, and military needs.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 8:46 p.m.