Triple

T8973979
Position Surface form Disambiguated ID Type / Status
Subject Liteyny Prospekt E214337 entity
Predicate crosses P416 FINISHED
Object Fontanka River E31589 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: Fontanka River | Statement: [Liteyny Prospekt, crosses, Fontanka River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fontanka River
Context triple: [Liteyny Prospekt, crosses, Fontanka River]
  • A. Fontanka River chosen
    The Fontanka River is a major distributary of the Neva in Saint Petersburg, Russia, known for its historic embankments, bridges, and role in defining the city’s central layout.
  • B. Yauza River
    The Yauza River is a small river in Moscow, Russia, that flows through the city’s northeastern districts before joining the Moskva River.
  • C. Okhta River
    The Okhta River is a tributary waterway in northwestern Russia that flows through Saint Petersburg before joining the Neva River.
  • D. Moika River
    The Moika River is a small, historic waterway in central Saint Petersburg, Russia, lined with notable palaces and landmarks and forming part of the city’s iconic canal network.
  • E. Bolshaya Nevka
    Bolshaya Nevka is a major distributary channel of the Neva River in Saint Petersburg, Russia, forming part of the city’s intricate river and canal network.
  • 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_69ca839dbf608190a2f5990477115d29 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6783abe48190840e652fc2acf28f completed April 1, 2026, 12:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69d139a069f881909cc59bad0f110830 completed April 4, 2026, 4:17 p.m.
Created at: March 30, 2026, 7:02 p.m.