Triple
T12664379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnoselskaya |
E302508
|
entity |
| Predicate | adjacentStation |
P5707
|
FINISHED |
| Object | Sokolniki |
E605645
|
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: Sokolniki | Statement: [Krasnoselskaya, adjacentStation, Sokolniki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sokolniki Context triple: [Krasnoselskaya, adjacentStation, Sokolniki]
-
A.
Sokolniki
Sokolniki is a Moscow Metro station on the Big Circle Line, serving the Sokolniki District in Russia’s capital.
-
B.
Sokolniki District
chosen
Sokolniki District is a municipal district in Moscow, Russia, known for its large historic park and recreational areas.
-
C.
Krylatskoye
Krylatskoye is a Moscow Metro station serving the Krylatskoye District in western Moscow, Russia.
-
D.
Pirogovo
Pirogovo is a settlement located near the Pirogovskoye Reservoir, known as a local residential and recreational area.
-
E.
Novogireyevo
Novogireyevo is a Moscow Metro station serving the Novogireyevo District in the eastern part of Moscow, Russia.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617e030881908444743b8a7e0d75 |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c7527c4819096c49a12dcba3c1a |
completed | May 2, 2026, 10:36 p.m. |
Created at: April 9, 2026, 5:19 p.m.