Triple
T17297402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wörlitz |
E419946
|
entity |
| Predicate | gardenDesignInfluence |
P25951
|
FINISHED |
| Object | English landscape garden |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: English landscape garden | Statement: [Wörlitz, gardenDesignInfluence, English landscape garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gardenDesignInfluence Context triple: [Wörlitz, gardenDesignInfluence, English landscape garden]
-
A.
hasLandscapeDesignInfluence
chosen
Indicates that one entity has influenced or shaped the landscape design style, principles, or features of another entity.
-
B.
gardensStyle
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
C.
designInfluenceOn
Indicates that one design, designer, or design-related factor has an effect on shaping, guiding, or altering another design or design outcome.
-
D.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
E.
gardenValue
Indicates that one entity assigns or possesses a particular value, worth, or importance in relation to a garden.
- F. None of above.
Provenance (3 batches)
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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438f82788819088ea796850552297 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.