Triple
T12825373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakhimovsky Prospekt |
E306636
|
entity |
| Predicate | hasExitTo |
P29827
|
FINISHED |
| Object | Kakhovka Street |
E874890
|
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: Kakhovka Street | Statement: [Nakhimovsky Prospekt, hasExitTo, Kakhovka Street]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kakhovka Street Context triple: [Nakhimovsky Prospekt, hasExitTo, Kakhovka Street]
-
A.
Kakhovka Street
chosen
Kakhovka Street is a notable thoroughfare in Moscow, Russia, known for giving its name to the Kakhovskaya metro station and the surrounding district.
-
B.
Kirovogradskaya Street
Kirovogradskaya Street is a street in Moscow, Russia, known for serving as one of the access points to the Yuzhnaya metro station.
-
C.
Lenivka Street
Lenivka Street is a historic street in central Moscow, Russia, situated near major cultural and governmental landmarks.
-
D.
Azovskaya Street
Azovskaya Street is a local street in Moscow, Russia, situated near and connected to the major thoroughfare Nakhimovsky Prospekt.
-
E.
Kalanchevskaya Street
Kalanchevskaya Street is a major street in central Moscow, Russia, situated near the city’s main railway terminals and forming part of a key transport hub.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96facb2d48190bc12efc00c9da360 |
completed | April 10, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa11c81f481909129eef69e47d079 |
completed | May 9, 2026, 9:03 p.m. |
Created at: April 9, 2026, 5:32 p.m.