Triple
T21606677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Александровский сад |
E533191
|
entity |
| Predicate | категорияОхраны |
P5067
|
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.
protectionCategory
Indicates a classification relationship where an entity is assigned to a specific type or level of protection based on defined protective criteria or rules.
-
B.
partOfProtectedAreaCategory
chosen
Indicates that one protected area belongs to, or is classified under, a specific protected area category.
-
C.
protectedCategory
Indicates that one entity is classified under a legally or formally recognized group that is granted special protection from discrimination or adverse treatment.
-
D.
safetyCategory
Indicates the classification of something according to its level or type of safety.
-
E.
officerCategory
Indicates the classification or type of officer role that an individual holds within an organization or system.
- 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.