Triple
T12134364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpukhovskaya |
E289014
|
entity |
| Predicate | hasTransferTo |
P17241
|
FINISHED |
| Object | Dobryninskaya |
E268422
|
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: Dobryninskaya | Statement: [Serpukhovskaya, hasTransferTo, Dobryninskaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dobryninskaya Context triple: [Serpukhovskaya, hasTransferTo, Dobryninskaya]
-
A.
Dobryninskaya
chosen
Dobryninskaya is a Moscow Metro station on the circular Koltsevaya Line, known for its Stalinist-era architecture and central location.
-
B.
Savyolovskaya
Savyolovskaya is a Moscow Metro station on the Big Circle Line, serving as part of the city’s modern orbital rapid transit network.
-
C.
Savyolovskaya
Savyolovskaya is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the northern part of the city.
-
D.
Voykovskaya
Voykovskaya is a Moscow Metro station serving the Zamoskvoretskaya Line in the northern part of the city.
-
E.
Zhdanovskaya
Zhdanovskaya was the former name of a Moscow Metro station now known as Vykhino.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9158c59e0819094d4522a107482b2 |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e4a573c8190b5dd6cc61849739b |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:49 p.m.