Triple
T11884521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushkinskaya metro station |
E282743
|
entity |
| Predicate | isPartOfInterchangeHub |
P84508
|
FINISHED |
| Object | Pushkinskaya–Tverskaya–Chekhovskaya interchange node |
E898156
|
NE FINISHED |
How this triple was built (3 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–Tverskaya–Chekhovskaya interchange node | Statement: [Pushkinskaya metro station, isPartOfInterchangeHub, Pushkinskaya–Tverskaya–Chekhovskaya interchange node]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pushkinskaya–Tverskaya–Chekhovskaya interchange node Context triple: [Pushkinskaya metro station, isPartOfInterchangeHub, Pushkinskaya–Tverskaya–Chekhovskaya interchange node]
-
A.
Pushkinskaya–Chekhovskaya–Tverskaya interchange node
chosen
The Pushkinskaya–Chekhovskaya–Tverskaya interchange node is a major three-line transfer complex in the Moscow Metro that links the Tagansko-Krasnopresnenskaya, Serpukhovsko-Timiryazevskaya, and Zamoskvoretskaya lines in central Moscow.
-
B.
Sennaya–Sadovaya–Spasskaya interchange node
The Sennaya–Sadovaya–Spasskaya interchange node is a major three-line transfer hub in the Saint Petersburg Metro, connecting stations on different lines in the historic city center.
-
C.
Sokolnichesky Radius Interchange Stations
Sokolnichesky Radius Interchange Stations are a group of Moscow Metro transfer stations on the Big Circle Line that provide key connections to the Sokolnicheskaya (Sokolniki) radial line.
-
D.
Ploshcha Lenina–Vakzalnaja interchange
Ploshcha Lenina–Vakzalnaja interchange is a major transfer hub in the Minsk Metro system connecting key central stations and serving the city’s main railway terminal area.
-
E.
Frunzenskaya–Nyamiha interchange
Frunzenskaya–Nyamiha interchange is a major transfer hub in the Minsk Metro system connecting key central lines for passenger transfers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfInterchangeHub Context triple: [Pushkinskaya metro station, isPartOfInterchangeHub, Pushkinskaya–Tverskaya–Chekhovskaya interchange node]
-
A.
isPartOfInterchangeComplex
chosen
Indicates that one transportation facility or component belongs to and functions within a larger interchange complex.
-
B.
isCentralHubOf
Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
-
C.
isTransportHubType
Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
-
D.
isTransportationHubCodeFor
Indicates that a given code uniquely identifies and represents a specific transportation hub, such as a station, airport, or terminal.
-
E.
hasInterchangeStationWith
Indicates that two transportation lines, routes, or systems share a station where passengers can transfer between them.
- F. None of above.
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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a02ad4819090faef0e0be732ee |
completed | April 10, 2026, 10:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f281f488a8819082f40dfdd12f29a2 |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.