Triple
T30166480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Вознесенский проспект |
E766805
|
entity |
| Predicate | имеетОбъектНаУлице |
P150728
|
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.
hasOutdoorLocation
Indicates that an entity is associated with or possesses a specific outdoor place or setting.
-
B.
hasOutdoorFocus
Indicates a relationship where an entity is primarily concerned with, oriented toward, or specialized in outdoor environments, activities, or contexts.
-
C.
hasOutdoorSpaceType
Indicates the specific kind of outdoor area associated with an entity, such as a balcony, terrace, garden, or patio.
-
D.
hasPublicSquareInFront
Indicates that a building or structure has a public square located directly in front of it.
-
E.
hasOutdoorType
chosen
Indicates that an entity is associated with a specific type or category of outdoor environment or feature.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f073dbc8190a42f4c71ad2f7de3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:23 p.m.