Triple
T37433545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Bernhard Culture Fund Award for Garden Architecture |
E930205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | garden architecture award |
C17844
|
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: garden architecture award Context triple: [Prince Bernhard Culture Fund Award for Garden Architecture, instanceOf, garden architecture award]
-
A.
landscape architecture award
chosen
A landscape architecture award is a formal recognition given to outstanding projects or professionals who demonstrate excellence, innovation, and environmental sensitivity in the design and planning of outdoor spaces.
-
B.
architecture and design award
An architecture and design award is a formal recognition given to outstanding projects, professionals, or innovations that exemplify excellence, creativity, and impact in the fields of architecture and design.
-
C.
horticultural award
A horticultural award is a formal recognition given to individuals, organizations, or projects for outstanding achievement, innovation, or contribution in gardening, plant cultivation, or landscape design.
-
D.
Gartenkunstwerk
A Gartenkunstwerk is a designed garden or landscape conceived as a unified work of art, where plants, structures, and spatial composition are intentionally arranged to create aesthetic, cultural, and experiential meaning.
-
E.
garden design project
A garden design project is a planned endeavor that organizes and coordinates the creation or transformation of an outdoor space to achieve specific aesthetic, functional, and environmental goals.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.