Triple
T11953561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chekhovskaya |
E284489
|
entity |
| Predicate | hasTransferTo |
P17241
|
FINISHED |
| Object | Pushkinskaya |
E899331
|
NE FINISHED |
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: [Chekhovskaya, hasTransferTo, Pushkinskaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pushkinskaya Context triple: [Chekhovskaya, hasTransferTo, Pushkinskaya]
-
A.
Pushkinskaya
chosen
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.
-
B.
Kashirskaya
Kashirskaya is a Moscow Metro station that serves as an interchange point on the system’s Big Circle Line.
-
C.
Kaluzhskaya
Kaluzhskaya is a Moscow Metro station on the Kaluzhsko–Rizhskaya line, serving the southwestern part of the city.
-
D.
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.
-
E.
Gorkovskaya
Gorkovskaya was the former name of Moscow’s central Tverskaya metro station, reflecting its Soviet-era designation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90365da288190a132703df563de23 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f4590584608190bc00840c43f115a0 |
completed | May 1, 2026, 7:40 a.m. |
Created at: April 8, 2026, 9:45 p.m.