Triple
T11334063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dobryninskaya |
E268422
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Serpukhovskaya |
E289014
|
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: Serpukhovskaya | Statement: [Dobryninskaya, formerName, Serpukhovskaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Serpukhovskaya Context triple: [Dobryninskaya, formerName, Serpukhovskaya]
-
A.
Serpukhovskaya
chosen
Serpukhovskaya is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in central Moscow.
-
B.
Kashirskaya
Kashirskaya is a Moscow Metro station that serves as an interchange point on the system’s Big Circle Line.
-
C.
Volokolamskaya
Volokolamskaya is a Moscow Metro station on the Arbatsko–Pokrovskaya Line serving the northwestern 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.
Rizhskaya
Rizhskaya is a Moscow Metro station on the Big Circle Line serving the Rizhsky railway terminal area.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fe5d5881908d786b212a554d8b |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5432abfd081909d1bbf6460643fb9 |
completed | April 19, 2026, 9:03 p.m. |
Created at: April 8, 2026, 9:33 p.m.