Triple
T13155242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaluzhsko–Rizhskaya Line |
E312566
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object |
Sukharevskaya
Sukharevskaya is a Moscow Metro station on the Kaluzhsko–Rizhskaya Line, located near the historic Sukharev Square in central Moscow.
|
E1050320
|
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: Sukharevskaya | Statement: [Kaluzhsko–Rizhskaya Line, hasStation, Sukharevskaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sukharevskaya Context triple: [Kaluzhsko–Rizhskaya Line, hasStation, Sukharevskaya]
-
A.
Paveletskaya
Paveletskaya is a Moscow Metro station named after the nearby Paveletsky railway terminal, serving as a key transport hub in the city’s network.
-
B.
Karamyshevskaya
Karamyshevskaya is a metro station on Moscow’s Big Circle Line, serving the Khoroshyovo-Mnyovniki area of the city.
-
C.
Khoroshevskaya
Khoroshevskaya is a Moscow Metro station located on the Big Circle Line, serving the Khoroshyovsky District of the city.
-
D.
Voykovskaya
Voykovskaya is a Moscow Metro station serving the Zamoskvoretskaya Line in the northern part of the city.
-
E.
Piotrovskaya
Piotrovskaya is the feminine form of the Russian surname Piotrovsky, typically used for women in Russian naming conventions.
- 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: Sukharevskaya Triple: [Kaluzhsko–Rizhskaya Line, hasStation, Sukharevskaya]
Generated description
Sukharevskaya is a Moscow Metro station on the Kaluzhsko–Rizhskaya Line, located near the historic Sukharev Square in central Moscow.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Sukharevskaya Target entity description: Sukharevskaya is a Moscow Metro station on the Kaluzhsko–Rizhskaya Line, located near the historic Sukharev Square in central Moscow.
-
A.
Paveletskaya
Paveletskaya is a Moscow Metro station named after the nearby Paveletsky railway terminal, serving as a key transport hub in the city’s network.
-
B.
Karamyshevskaya
Karamyshevskaya is a metro station on Moscow’s Big Circle Line, serving the Khoroshyovo-Mnyovniki area of the city.
-
C.
Khoroshevskaya
Khoroshevskaya is a Moscow Metro station located on the Big Circle Line, serving the Khoroshyovsky District of the city.
-
D.
Voykovskaya
Voykovskaya is a Moscow Metro station serving the Zamoskvoretskaya Line in the northern part of the city.
-
E.
Piotrovskaya
Piotrovskaya is the feminine form of the Russian surname Piotrovsky, typically used for women in Russian naming conventions.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c06ccb881909390df18e1a6f7ed |
completed | April 10, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f7696f0819094825b158e1e9a8c |
completed | May 3, 2026, 5:01 p.m. |
| NEDg | Description generation | batch_69f7800caaf0819085e553f96a9f99cf |
completed | May 3, 2026, 5:04 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f78089050c81909943164d1a41a37f |
completed | May 3, 2026, 5:06 p.m. |
Created at: April 9, 2026, 9:12 p.m.