Triple
T14714456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hevsel Gardens |
E345640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic agricultural landscape |
C5419
|
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 agricultural landscape Context triple: [Hevsel Gardens, instanceOf, historic agricultural landscape]
-
A.
rural historic landscape
A rural historic landscape is a geographically defined area of countryside whose land use, features, and spatial organization reflect the historical patterns, activities, and cultural values of the people who shaped it over time.
-
B.
agricultural landscape
chosen
An agricultural landscape is a rural area shaped by human cultivation and management, featuring fields, pastures, and related infrastructure used for the production of crops and livestock.
-
C.
historic farmstead
A historic farmstead is a preserved agricultural property, including its farmhouse, outbuildings, fields, and landscape features, that collectively illustrate the farming practices, architecture, and rural life of a particular period in history.
-
D.
historic communal farm
A historic communal farm is a shared agricultural property where a community of people collectively lived and worked the land, reflecting past social, economic, and cultural practices of cooperative rural life.
-
E.
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.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:29 a.m.