Triple
T19425779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River Valley estates |
E485975
|
entity |
| Predicate | landscapeDesignFeatures |
P45658
|
FINISHED |
| Object | terraced lawns |
—
|
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: terraced lawns | Statement: [Hudson River Valley estates, landscapeDesignFeatures, terraced lawns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landscapeDesignFeatures Context triple: [Hudson River Valley estates, landscapeDesignFeatures, terraced lawns]
-
A.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
B.
rockGardenDesignFeature
Indicates that something serves as a design feature or element within a rock garden.
-
C.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
D.
landscapeElement
chosen
Indicates that one entity functions as a landscape-related feature or component in relation to another entity.
-
E.
ornamentalFeature
Indicates that one entity serves as a decorative or embellishing feature of another entity.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63218772c8190a48b6cb01bd12b73 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.