Triple

T2649077
Position Surface form Disambiguated ID Type / Status
Subject Valdai Hills E53853 entity
Predicate riverSource P12617 FINISHED
Object Tvertsa River E348253 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: Tvertsa River | Statement: [Valdai Hills, riverSource, Tvertsa River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tvertsa River
Context triple: [Valdai Hills, riverSource, Tvertsa River]
  • A. Tvertsa River chosen
    The Tvertsa River is a waterway in western Russia that flows through Tver Oblast and serves as a tributary of the Volga River.
  • B. Tsaritsa River
    The Tsaritsa River is a waterway in Volgograd, Russia, historically significant as the small river along which the city’s predecessor, Tsaritsyn, developed.
  • C. Votka River
    The Votka River is a smaller watercourse in Russia that feeds into the larger Kama River within the Volga basin.
  • D. Vetluga River
    The Vetluga River is a significant waterway in western Russia that flows through several regions before joining the Volga River.
  • 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_69ab495e192081909c77b622e8e7e15a completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd91ca1288190ba302b04bac4c153 completed March 7, 2026, 7:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69b402a702a081909319ba32990fa010 completed March 13, 2026, 12:27 p.m.
Created at: March 6, 2026, 9:53 p.m.