Triple
T30436197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дом Советов РСФСР |
E774317
|
entity |
| Predicate | расположенНаУлице |
P105947
|
FINISHED |
| Object | Краснопресненская набережная |
—
|
NE NERFINISHED |
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.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
B.
расположенаНа
chosen
Indicates that one entity is located on the surface or area of another entity.
-
C.
hasOutdoorLocation
Indicates that an entity is associated with or possesses a specific outdoor place or setting.
-
D.
isOutdoorFriendly
Indicates that something is suitable for use, presence, or activity in outdoor environments without causing problems or undue risk.
-
E.
hasOutdoorSpaceType
Indicates the specific kind of outdoor area associated with an entity, such as a balcony, terrace, garden, or patio.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:07 p.m.