Triple
T10213710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Renaissance gardens |
E242391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical garden type |
C5306
|
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: historical garden type Context triple: [Italian Renaissance gardens, instanceOf, historical garden type]
-
A.
historic garden
chosen
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.
-
B.
formal garden
A formal garden is a carefully designed outdoor space characterized by symmetrical layouts, geometric shapes, and meticulously maintained plants arranged to create order and visual harmony.
-
C.
horticultural garden
A horticultural garden is a purposefully designed outdoor space where a diverse range of plants is cultivated, displayed, and studied for education, conservation, research, and aesthetic enjoyment.
-
D.
legendary garden
A legendary garden is a mythical or historically renowned cultivated space celebrated for its extraordinary beauty, rare flora, and enduring cultural or symbolic significance.
-
E.
historic estate type
A historic estate type is a classification of large, historically significant residential properties characterized by their architectural style, period of construction, original function, and cultural or social importance.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:03 a.m.