Triple

T7373215
Position Surface form Disambiguated ID Type / Status
Subject Mariinsky Palace E170058 entity
Predicate near P350 FINISHED
Object Moika River E32085 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: Moika River | Statement: [Mariinsky Palace, near, Moika River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moika River
Context triple: [Mariinsky Palace, near, Moika River]
  • A. Moika River chosen
    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.
  • B. Okhta River
    The Okhta River is a tributary waterway in northwestern Russia that flows through Saint Petersburg before joining the Neva River.
  • C. Fontanka River
    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.
  • D. Msta River
    The Msta River is a waterway in northwestern Russia that flows from the Valdai Hills through the Novgorod and Tver regions before joining the Volkhov River basin.
  • E. Moskva River
    The Moskva River is a major waterway in western Russia that flows through and gives its name to the capital city, 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_69c68a5bfaac81909ce7f001dfb70c76 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f1a50898819087097a64e09e19eb completed March 27, 2026, 9:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c84ee2397481909552cec2d4b90cc5 completed March 28, 2026, 9:57 p.m.
Created at: March 27, 2026, 3:07 p.m.