Triple
T34211882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zyablikovo |
E877677
|
entity |
| Predicate | interchangeLine |
P42836
|
FINISHED |
| Object | Zamoskvoretskaya Line |
—
|
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: Zamoskvoretskaya Line | Statement: [Zyablikovo, interchangeLine, Zamoskvoretskaya Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interchangeLine Context triple: [Zyablikovo, interchangeLine, Zamoskvoretskaya Line]
-
A.
interchangeWithLine
chosen
Indicates that one entity can be transferred or switched to another specific line, such as a route, track, or service line, at a given point.
-
B.
interchangeSystem
Indicates a relationship where two or more systems are connected in such a way that they can exchange or transfer items, data, or services between them.
-
C.
interchangeLocation
Indicates a location where two or more routes, lines, or modes of transport connect, allowing passengers or goods to transfer between them.
-
D.
lineReplaced
Indicates that one line has been substituted or superseded by another line, typically in a versioning, editing, or modification context.
-
E.
lineTranslation
Indicates a transformation that maps one line to another while preserving its linear structure and relative positioning.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 1, 2026, 1:55 a.m.