Triple

T13572415
Position Surface form Disambiguated ID Type / Status
Subject Troparyovo E324195 entity
Predicate hasEntrance P6140 FINISHED
Object Leninsky Prospekt E212913 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: Leninsky Prospekt | Statement: [Troparyovo, hasEntrance, Leninsky Prospekt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leninsky Prospekt
Context triple: [Troparyovo, hasEntrance, Leninsky Prospekt]
  • A. Leninsky Prospekt chosen
    Leninsky Prospekt is a major avenue in Moscow, Russia, known for its wide thoroughfare, Soviet-era architecture, and prominent landmarks.
  • B. Leninsky Prospekt
    Leninsky Prospekt is a major avenue and transport artery in Saint Petersburg, Russia, known for connecting residential districts with the city’s broader road network.
  • C. Nakhimovsky Prospekt
    Nakhimovsky Prospekt is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the south of Moscow.
  • D. Kutuzovsky Prospekt
    Kutuzovsky Prospekt is a major, historically significant avenue in Moscow known for its wide thoroughfare, Stalin-era architecture, and role as a key route into the city center.
  • E. Moskovsky Prospekt
    Moskovsky Prospekt is one of Saint Petersburg’s major radial avenues, serving as a key thoroughfare connecting the city center with its southern districts and the route toward Moscow.
  • 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_69d80769100c819099111274614f5ed2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb0106cb48190b20eb9bda131a68a completed April 12, 2026, 2:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00a4fffa7c81909bcc833b44ddf66f completed May 10, 2026, 3:32 p.m.
Created at: April 9, 2026, 9:48 p.m.