Triple
T10984958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tverskaya |
E259604
|
entity |
| Predicate | hasTransferTo |
P17241
|
FINISHED |
| Object |
Pushkinskaya
Pushkinskaya is a Moscow Metro station located in the city center, known for serving the busy Tverskaya area and providing convenient transfers on the network.
|
E899331
|
NE FINISHED |
How this triple was built (4 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: [Tverskaya, hasTransferTo, Pushkinskaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pushkinskaya Context triple: [Tverskaya, hasTransferTo, Pushkinskaya]
-
A.
Kashirskaya
Kashirskaya is a Moscow Metro station that serves as an interchange point on the system’s Big Circle Line.
-
B.
Kaluzhskaya
Kaluzhskaya is a Moscow Metro station on the Kaluzhsko–Rizhskaya line, serving the southwestern part of the city.
-
C.
Krasnopresnenskaya
Krasnopresnenskaya is a Moscow Metro station on the city’s circular Koltsevaya Line, known for its deep-level construction and Soviet-era architectural design.
-
D.
Khoroshevskaya
Khoroshevskaya is a Moscow Metro station located on the Big Circle Line, serving the Khoroshyovsky District of the city.
-
E.
Kolomenskaya
Kolomenskaya is a Moscow Metro station on the Zamoskvoretskaya Line, serving the Kolomenskoye area in the southern part of the city.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Pushkinskaya Triple: [Tverskaya, hasTransferTo, Pushkinskaya]
Generated description
Pushkinskaya is a Moscow Metro station located in the city center, known for serving the busy Tverskaya area and providing convenient transfers on the network.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Pushkinskaya Target entity description: Pushkinskaya is a Moscow Metro station located in the city center, known for serving the busy Tverskaya area and providing convenient transfers on the network.
-
A.
Kashirskaya
Kashirskaya is a Moscow Metro station that serves as an interchange point on the system’s Big Circle Line.
-
B.
Kaluzhskaya
Kaluzhskaya is a Moscow Metro station on the Kaluzhsko–Rizhskaya line, serving the southwestern part of the city.
-
C.
Krasnopresnenskaya
Krasnopresnenskaya is a Moscow Metro station on the city’s circular Koltsevaya Line, known for its deep-level construction and Soviet-era architectural design.
-
D.
Khoroshevskaya
Khoroshevskaya is a Moscow Metro station located on the Big Circle Line, serving the Khoroshyovsky District of the city.
-
E.
Kolomenskaya
Kolomenskaya is a Moscow Metro station on the Zamoskvoretskaya Line, serving the Kolomenskoye area in the southern part of the city.
- F. None of above. chosen
Provenance (5 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772ed1eb88190b7333b746f76a088 |
completed | April 9, 2026, 9:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e374526d54819085a0fb0d62f7a581 |
completed | April 18, 2026, 12:08 p.m. |
| NEDg | Description generation | batch_69e378dcc92c8190952d4acfee2a309c |
completed | April 18, 2026, 12:28 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69e37be75a588190abb9569ef1e87279 |
completed | April 18, 2026, 12:41 p.m. |
Created at: April 8, 2026, 9:24 p.m.