Triple

T21632002
Position Surface form Disambiguated ID Type / Status
Subject Third Ring Road E533853 entity
Predicate hasJunctionWith P1018 FINISHED
Object Leninsky Prospekt 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: Leninsky Prospekt | Statement: [Third Ring Road, hasJunctionWith, Leninsky Prospekt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leninsky Prospekt
Context triple: [Third Ring Road, hasJunctionWith, 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. Krasny Prospekt
    Krasny Prospekt is a metro station in Novosibirsk, Russia, serving one of the city’s main central thoroughfares.
  • 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_69e0c465ae7481908577b7209fdb2a77 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef5217952c8190910c2103fb4a27d9 completed April 27, 2026, 12:09 p.m.
Created at: April 16, 2026, 6:34 p.m.