Triple

T13950413
Position Surface form Disambiguated ID Type / Status
Subject Upper Volga E335505 entity
Predicate hasTributary P415 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: [Upper Volga, hasTributary, Tvertsa River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tvertsa River
Context triple: [Upper Volga, hasTributary, 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. Vokhma River
    The Vokhma River is a smaller watercourse in Russia that serves as one of the tributaries feeding into the larger Vetluga River system.
  • E. Kirzhach River
    The Kirzhach River is a waterway in Vladimir Oblast, Russia, known for its scenic, forested banks and recreational boating and fishing.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e131c608190b4ffdbada24a3208 completed April 14, 2026, 12:07 p.m.
NED1 Entity disambiguation (via context triple) batch_6a004f3548b48190aec852723654bd35 completed May 10, 2026, 9:26 a.m.
Created at: April 9, 2026, 10:17 p.m.