Triple

T4182324
Position Surface form Disambiguated ID Type / Status
Subject Saint Petersburg Oblast E88221 entity
Predicate contains P35 FINISHED
Object Svir River E106206 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: Svir River | Statement: [Saint Petersburg Oblast, contains, Svir River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Svir River
Context triple: [Saint Petersburg Oblast, contains, Svir River]
  • A. Svir River chosen
    The Svir River is a waterway in northwestern Russia that links Lake Onega to Lake Ladoga and forms part of the Volga–Baltic waterway system.
  • B. Votka River
    The Votka River is a smaller watercourse in Russia that feeds into the larger Kama River within the Volga basin.
  • C. Neisse River
    The Neisse River is a Central European river that forms part of the border between Germany and Poland before joining the Oder River.
  • D. Razdolnaya River
    The Razdolnaya River is a transboundary river in Northeast Asia that flows from northeastern China into Russia’s Primorsky Krai before emptying into the Sea of Japan.
  • E. Vishera River
    The Vishera River is a significant waterway in Russia’s Perm Krai, known for its scenic, largely untouched natural landscapes and role in the regional river system.
  • 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_69aed9477e8c81908bcb862d2db55b1d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af0305e2e88190a51f176f8534f1f9 completed March 9, 2026, 5:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69bb80ac75448190a2f6724c11eabef3 completed March 19, 2026, 4:50 a.m.
Created at: March 9, 2026, 3:45 p.m.