Triple
T21606660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Александровский сад |
E533191
|
entity |
| Predicate | имеетВход |
P6140
|
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.
hasEntrance
chosen
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
B.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
C.
ранееВходилоВ
Indicates that an entity previously belonged to, was part of, or was included within another entity, but is no longer included in it.
-
D.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
-
E.
entersFrom
Indicates that one entity moves into or arrives at a place, state, or context by coming from another specified source or location.
- 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.