Triple
T37941956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Тимирязевская |
E946510
|
entity |
| Predicate | направление линии к югу |
P103228
|
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.
lineDirectionSouth
chosen
Indicates that a line or path is oriented or directed toward the south.
-
B.
directionInSouthernHemisphere
Indicates that the specified direction is defined or measured relative to locations or reference frames in the Southern Hemisphere.
-
C.
линия
Indicates a relationship where something is a line or forms a linear connection or boundary between points or areas.
-
D.
lineDirectionTo
Indicates the directional relationship from one line to another, such as whether they point in the same, opposite, or a specific relative direction.
-
E.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.