Triple
T21606664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Александровский сад |
E533191
|
entity |
| Predicate | стильБлагоустройства |
P54626
|
FINISHED |
| Object | классический ландшафтный парк |
—
|
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: классический ландшафтный парк | Statement: [Александровский сад, стильБлагоустройства, классический ландшафтный парк]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: стильБлагоустройства Context triple: [Александровский сад, стильБлагоустройства, классический ландшафтный парк]
-
A.
gardensStyle
chosen
Indicates the stylistic design or aesthetic tradition according to which a garden is created or arranged.
-
B.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
C.
ornamentalFeature
Indicates that one entity serves as a decorative or embellishing feature of another entity.
-
D.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
E.
plantingStyle
Indicates the method or arrangement used to plant entities in relation to each other or their 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e5783481909db36c388f3ae227 |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.