Triple
T36456168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushkinskaya–Chekhovskaya–Tverskaya interchange node |
E898156
|
entity |
| Predicate | namedAfterStation |
P63
|
FINISHED |
| Object | Pushkinskaya |
—
|
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: Pushkinskaya | Statement: [Pushkinskaya–Chekhovskaya–Tverskaya interchange node, namedAfterStation, Pushkinskaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterStation Context triple: [Pushkinskaya–Chekhovskaya–Tverskaya interchange node, namedAfterStation, Pushkinskaya]
-
A.
formerStationNameFor
Indicates that one station name was previously used as the official name for another station.
-
B.
hasSuccessorStationName
Indicates that one station is immediately followed by another station, whose name is given as the successor station name.
-
C.
namesakeStation
Indicates that one entity is a station that shares the same name as, or is named after, another entity.
-
D.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
E.
namedAfterDirection
Indicates that something is given a name derived from a cardinal or relative direction (e.g., north, south, eastern, western).
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:10 p.m.