Triple

T11389017
Position Surface form Disambiguated ID Type / Status
Subject Tretyakovskaya E269783 entity
Predicate locatedNear P294 FINISHED
Object Lavrushinsky Lane E804654 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: Lavrushinsky Lane | Statement: [Tretyakovskaya, locatedNear, Lavrushinsky Lane]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lavrushinsky Lane
Context triple: [Tretyakovskaya, locatedNear, Lavrushinsky Lane]
  • A. Lavrushinsky Lane chosen
    Lavrushinsky Lane is a historic street in central Moscow best known as the location of the State Tretyakov Gallery’s main building.
  • B. Chaikovskoho Lane
    Chaikovskoho Lane is a street in central Odesa, Ukraine, known for hosting the historic Odesa Opera and Ballet Theater.
  • C. Balaklavsky Avenue
    Balaklavsky Avenue is a major thoroughfare in Moscow, Russia, running through the city’s southern districts and serving as an important urban transport artery.
  • D. Polyanka Street
    Polyanka Street is a central Moscow thoroughfare known for its historic architecture and role as a major urban transport route.
  • E. Yauzsky Boulevard
    Yauzsky Boulevard is a historic tree-lined boulevard in central Moscow that forms part of the city’s Boulevard Ring and runs near the Yauza River.
  • 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_69d6aacdbc6c8190af6dc3d5f5d22836 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7fc389d4c81909515a5c8b0099c36 completed April 9, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f470faab4c8190ac9091713080dc7a completed May 1, 2026, 9:23 a.m.
Created at: April 8, 2026, 9:34 p.m.