Triple

T12144597
Position Surface form Disambiguated ID Type / Status
Subject Okhotny Ryad Street E289283 entity
Predicate connects P390 FINISHED
Object Teatralny Proyezd E344384 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: Teatralny Proyezd | Statement: [Okhotny Ryad Street, connects, Teatralny Proyezd]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Teatralny Proyezd
Context triple: [Okhotny Ryad Street, connects, Teatralny Proyezd]
  • A. Teatralny Proyezd chosen
    Teatralny Proyezd is a central Moscow street near the city’s main theaters and historic squares, forming part of the capital’s cultural and architectural core.
  • B. Tsvetnoy Bulvar
    Tsvetnoy Bulvar is a Moscow Metro station located near the historic Tsvetnoy Boulevard in central Moscow, serving as a key transit point in the city’s underground network.
  • C. Izmailovskaya
    Izmailovskaya was the original name of a Moscow Metro station later renamed Partizanskaya, located on the Arbatsko–Pokrovskaya line.
  • D. Michurinsky Prospekt
    Michurinsky Prospekt is a metro station on Moscow’s Big Circle Line serving the Michurinsky Prospekt area in the city’s western district.
  • E. Lermontovsky Prospekt
    Lermontovsky Prospekt is a major avenue in Saint Petersburg, Russia, known for its historic architecture and role as an important transport artery in the city.
  • 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_69d6ab4c6710819097a9d228382dde43 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915aacaa08190b31f54e230334406 completed April 10, 2026, 3:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69feb7ca3e348190a75c1dd8aec73a40 completed May 9, 2026, 4:27 a.m.
Created at: April 8, 2026, 9:49 p.m.