Triple
T31675165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Хорошёвская |
E808379
|
entity |
| Predicate | оснащена |
P83948
|
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.
equippedFor
Indicates that one entity is suitably provided with the necessary tools, features, or capabilities to perform a particular function or handle a specific situation for another entity or purpose.
-
B.
designedToAccommodate
Indicates that something has been intentionally created or configured in a way that can suitably hold, support, or serve a particular thing, group, or purpose.
-
C.
fittedWith
chosen
Indicates that one entity is equipped, supplied, or provided with another entity as a component, feature, or accessory.
-
D.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
E.
hasAuxiliaryEquipment
Indicates that one entity is equipped with, or accompanied by, additional supporting equipment associated with another entity.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:02 p.m.