Triple
T11787473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dmitrovskaya |
E280306
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Dmitrovskoye Shosse |
E999953
|
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: Dmitrovskoye Shosse | Statement: [Dmitrovskaya, namedAfter, Dmitrovskoye Shosse]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dmitrovskoye Shosse Context triple: [Dmitrovskaya, namedAfter, Dmitrovskoye Shosse]
-
A.
Dmitrovskoye Shosse
chosen
Dmitrovskoye Shosse is a major radial highway in Moscow that connects the city center with its northern suburbs and outlying regions.
-
B.
Mozhayskoye Shosse
Mozhayskoye Shosse is a major highway in western Moscow that continues the city’s main radial route toward the Mozhaysk and Smolensk directions.
-
C.
Pyatnitskoye Shosse
Pyatnitskoye Shosse is a Moscow Metro station serving as the northwestern terminus of the Arbatsko–Pokrovskaya Line.
-
D.
Aminyevskoye Shosse
Aminyevskoye Shosse is a major roadway in Moscow, Russia, serving as an important transport artery in the city’s western districts.
-
E.
Borovskoye Shosse
Borovskoye Shosse is a Moscow Metro station on the Kalininsko–Solntsevskaya line serving the Borovskoye Highway area in western Moscow.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a586803481909af0032c35ca6e51 |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68e9b70d08190aa74e612947317b5 |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 8, 2026, 9:42 p.m.