Triple
T36452117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elektrozavodskaya (Arbatsko–Pokrovskaya Line) |
E898038
|
entity |
| Predicate | adjacentStationTowardsEast |
P192606
|
FINISHED |
| Object | Semyonovskaya |
—
|
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: Semyonovskaya | Statement: [Elektrozavodskaya (Arbatsko–Pokrovskaya Line), adjacentStationTowardsEast, Semyonovskaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentStationTowardsEast Context triple: [Elektrozavodskaya (Arbatsko–Pokrovskaya Line), adjacentStationTowardsEast, Semyonovskaya]
-
A.
adjacentStationTowards
Indicates that one station is directly next to another station in a specified direction along a route or line.
-
B.
adjacentStationWest
Indicates that one station is immediately to the west of another station in a spatial or network layout.
-
C.
adjacentStationTowardsSouth
Indicates that one station is directly next to another in the southward direction along a route or line.
-
D.
adjacentStationNorth
Indicates that one station is directly adjacent to another station to its north.
-
E.
adjacentStationSouth
Indicates that one station is directly to the south of another station, with no other station in between.
- F. None of above. chosen
Provenance (4 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: May 3, 2026, 4:10 p.m.