Triple
T31675179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Хорошёвская |
E808379
|
entity |
| Predicate | расположенаМеждуСтанциями |
P168284
|
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.
betweenStation
Indicates a relationship where something (such as a route, segment, or connection) lies or operates between two stations.
-
B.
middleStation
chosen
Indicates that one station lies between two other stations along a route or line, serving as an intermediate point in the sequence.
-
C.
разположенНаГраницаМежду
Indicates that something is located on or along the boundary between two entities.
-
D.
servesAsThroughStationFor
Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
-
E.
расположенаНа
Indicates that one entity is located on the surface or area of 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:02 p.m.