Triple

T21185113
Position Surface form Disambiguated ID Type / Status
Subject Russian federal highway network E522059 entity
Predicate hasComponent P35 FINISHED
Object M-highways of Russia 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: M-highways of Russia | Statement: [Russian federal highway network, hasComponent, M-highways of Russia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M-highways of Russia
Context triple: [Russian federal highway network, hasComponent, M-highways of Russia]
  • A. Russian federal highway network
    The Russian federal highway network is a nationwide system of major roads that connects regions across the Russian Federation, supporting long-distance transportation, commerce, and strategic mobility.
  • B. 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.
  • C. M11 Moscow–Saint Petersburg motorway
    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.
  • D. 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.
  • E. N1 highway
    The N1 highway is a major national route in South Africa that runs roughly north–south, linking Cape Town with Johannesburg, Pretoria, and the Zimbabwean border.
  • 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: M-highways of Russia
Target entity description: The M-highways of Russia are major federal motorways that form the core long-distance road corridors connecting Moscow with key regions and international routes across the country.
  • A. Russian federal highway network chosen
    The Russian federal highway network is a nationwide system of major roads that connects regions across the Russian Federation, supporting long-distance transportation, commerce, and strategic mobility.
  • B. 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.
  • C. M11 Moscow–Saint Petersburg motorway
    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.
  • D. 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.
  • E. N1 highway
    The N1 highway is a major national route in South Africa that runs roughly north–south, linking Cape Town with Johannesburg, Pretoria, and the Zimbabwean border.
  • F. None of above.

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_69e0b50ef1d48190b063aa342667df22 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e730205ce88190b0bb33003295d6e7 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 3:06 p.m.