Triple
T11816890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tverskaya |
E281022
|
entity |
| Predicate | hasConnection |
P8776
|
FINISHED |
| Object | Chekhovskaya |
E284489
|
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: Chekhovskaya | Statement: [Tverskaya, hasConnection, Chekhovskaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chekhovskaya Context triple: [Tverskaya, hasConnection, Chekhovskaya]
-
A.
Chekhovskaya
chosen
Chekhovskaya is a Moscow Metro station located in the city center, known for its deep underground construction and convenient transfers to other central lines.
-
B.
Gorkovskaya
Gorkovskaya was the former name of Moscow’s central Tverskaya metro station, reflecting its Soviet-era designation.
-
C.
Sheremetevskaya
Sheremetevskaya is a Russian noble family name historically associated with the aristocracy of the Russian Empire.
-
D.
Khoroshevskaya
Khoroshevskaya is a Moscow Metro station located on the Big Circle Line, serving the Khoroshyovsky District of the city.
-
E.
Karamyshevskaya
Karamyshevskaya is a metro station on Moscow’s Big Circle Line, serving the Khoroshyovo-Mnyovniki area of the city.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e760988190b50d13bba5ef5b43 |
completed | April 10, 2026, 7:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f28110623481908354bdd4e437f99e |
completed | April 29, 2026, 10:07 p.m. |
Created at: April 8, 2026, 9:42 p.m.