Triple
T31675169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Хорошёвская |
E808379
|
entity |
| Predicate | имеетВыходК |
P43499
|
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.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
exitsThrough
chosen
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
-
C.
hasNumberOfExits
Indicates the relationship that specifies how many exits are associated with a given entity.
-
D.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
E.
doesNotHaveOutletTo
Indicates that one entity lacks any direct outlet, passage, or connection leading to another entity or to an external space.
- 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_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:02 p.m.