Triple
T19107187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M11 Neva motorway |
E467686
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | M11 Moscow–Saint Petersburg motorway |
—
|
NE NERFINISHED |
How this triple was built (3 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: M11 Moscow–Saint Petersburg motorway | Statement: [M11 Neva motorway, alsoKnownAs, M11 Moscow–Saint Petersburg motorway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M11 Moscow–Saint Petersburg motorway Context triple: [M11 Neva motorway, alsoKnownAs, M11 Moscow–Saint Petersburg motorway]
-
A.
Maikop–Tuapse highway
The Maikop–Tuapse highway is a regional road in southern Russia that links the inland city of Maykop with the Black Sea port town of Tuapse, crossing the foothills of the Caucasus.
-
B.
Moscow–Minsk highway
The Moscow–Minsk highway is a major international roadway connecting Russia’s capital Moscow with Belarus’s capital Minsk, forming part of a key transport corridor between Russia and Western Europe.
-
C.
Moscow–Domodedovo highway corridor
The Moscow–Domodedovo highway corridor is a major transport route in the Moscow region that connects the city with Domodedovo and its international airport, running parallel to key rail infrastructure.
-
D.
M5 Ural Highway
The M5 Ural Highway is a major federal road in Russia that connects Moscow with the Ural region, serving as a key east–west transport artery across several central and Volga federal districts.
-
E.
Nizhny Novgorod–Kirov highway
The Nizhny Novgorod–Kirov highway is a major regional road in Russia that links the city of Nizhny Novgorod with Kirov, serving as an important transport corridor for the surrounding areas.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: M11 Moscow–Saint Petersburg motorway Target entity description: The M11 Moscow–Saint Petersburg motorway is a major Russian toll expressway connecting the country’s capital, Moscow, with its second-largest city, Saint Petersburg, designed for high-speed, long-distance travel.
-
A.
Maikop–Tuapse highway
The Maikop–Tuapse highway is a regional road in southern Russia that links the inland city of Maykop with the Black Sea port town of Tuapse, crossing the foothills of the Caucasus.
-
B.
Moscow–Minsk highway
The Moscow–Minsk highway is a major international roadway connecting Russia’s capital Moscow with Belarus’s capital Minsk, forming part of a key transport corridor between Russia and Western Europe.
-
C.
Moscow–Domodedovo highway corridor
The Moscow–Domodedovo highway corridor is a major transport route in the Moscow region that connects the city with Domodedovo and its international airport, running parallel to key rail infrastructure.
-
D.
M5 Ural Highway
The M5 Ural Highway is a major federal road in Russia that connects Moscow with the Ural region, serving as a key east–west transport artery across several central and Volga federal districts.
-
E.
Nizhny Novgorod–Kirov highway
The Nizhny Novgorod–Kirov highway is a major regional road in Russia that links the city of Nizhny Novgorod with Kirov, serving as an important transport corridor for the surrounding areas.
- F. None of above. chosen
Provenance (2 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e391245c8190b1393577b61c4f76 |
completed | April 20, 2026, 8:28 a.m. |
Created at: April 10, 2026, 12:04 p.m.