Triple
T5003933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jardin archéologique de Cybèle |
E112439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological garden |
C8110
|
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: archaeological garden Context triple: [Jardin archéologique de Cybèle, instanceOf, archaeological garden]
-
A.
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.
-
B.
ethnobotanical park
An ethnobotanical park is a curated landscape that conserves and showcases plant species in the context of their traditional cultural, medicinal, and practical uses by local or indigenous communities.
-
C.
reconstructed historic site
chosen
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
-
D.
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.
-
E.
botanical garden building
A botanical garden building is a specialized structure designed to cultivate, display, and study diverse plant collections in controlled environments for education, conservation, and public enjoyment.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:35 p.m.