Triple
T6882281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosehill Cemetery |
E158825
|
entity |
| Predicate | hasLandscapeDesignStyle |
P1479
|
FINISHED |
| Object | picturesque landscape style |
—
|
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: picturesque landscape style | Statement: [Rosehill Cemetery, hasLandscapeDesignStyle, picturesque landscape style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandscapeDesignStyle Context triple: [Rosehill Cemetery, hasLandscapeDesignStyle, picturesque landscape style]
-
A.
hasLandscapeDesignInfluence
Indicates that one entity has influenced or shaped the landscape design style, principles, or features of another entity.
-
B.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
C.
hasLandscaping
Indicates that an entity possesses or is associated with designed outdoor grounds or landscape features.
-
D.
gardensStyle
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
E.
landscapeStyle
chosen
Indicates the design style or aesthetic approach applied to a landscape or outdoor environment.
- 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_69c688342f6c8190ad7eea6ba262db99 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8e90c9481908d00634f67fa71f8 |
completed | March 27, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:23 p.m.