Triple
T8816313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage tentative list (Droogmakerij de Beemster and related works context) |
E209785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural landscape proposal |
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: cultural landscape proposal Context triple: [UNESCO World Heritage tentative list (Droogmakerij de Beemster and related works context), instanceOf, cultural landscape proposal]
-
A.
cultural site
A cultural site is a place of historical, artistic, social, or spiritual significance that embodies and preserves the traditions, values, and heritage of a community or civilization.
-
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.
land use plan
A land use plan is a strategic document that guides the allocation, development, and conservation of land within a defined area to balance environmental, social, and economic objectives.
-
D.
landmark planning blueprint
A landmark planning blueprint is a strategic, visual, and documented plan that outlines the design, placement, significance, and long-term development of key landmarks within a geographic or urban context.
-
E.
cultural heritage survey
A cultural heritage survey is a systematic assessment and documentation of a community’s tangible and intangible cultural resources to understand, preserve, and manage them for present and future generations.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:45 p.m.