Triple

T20008432
Position Surface form Disambiguated ID Type / Status
Subject Garden Ring transport system E494522 entity
Predicate hasLocalName P6353 FINISHED
Object Садовое кольцо NE NERFINISHED

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: Садовое кольцо | Statement: [Garden Ring transport system, hasLocalName, Садовое кольцо]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Садовое кольцо
Context triple: [Garden Ring transport system, hasLocalName, Садовое кольцо]
  • A. Садовое кольцо chosen
    Садовое кольцо is a major circular avenue encircling central Moscow, known as one of the city’s key transport and historical thoroughfares.
  • B. Pyatnitskoye Shosse
    Pyatnitskoye Shosse is a Moscow Metro station serving as the northwestern terminus of the Arbatsko–Pokrovskaya Line.
  • C. Dmitrovskoye Shosse
    Dmitrovskoye Shosse is a major radial highway in Moscow that connects the city center with its northern suburbs and outlying regions.
  • D. Okhotny Ryad
    Okhotny Ryad is a central Moscow street and area near the Kremlin known for its historic significance, government buildings, and major shopping complexes.
  • E. Slavyansky Bulvar
    Slavyansky Bulvar is a Moscow Metro station serving the western part of the city, named after the nearby Slavyansky Boulevard.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69da626b2d748190886981ea90c8b2ea completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e661a7500481908b69f74e479f88c8 completed April 20, 2026, 5:25 p.m.
Created at: April 11, 2026, 3:33 p.m.