Triple

T17967034
Position Surface form Disambiguated ID Type / Status
Subject Yuronga River E449237 entity
Predicate tributaryOf P415 FINISHED
Object Vetluga River NE NERFINISHED

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: Vetluga River | Statement: [Yuronga River, tributaryOf, Vetluga River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vetluga River
Context triple: [Yuronga River, tributaryOf, Vetluga River]
  • A. Vetluga River chosen
    The Vetluga River is a significant waterway in western Russia that flows through several regions before joining the Volga River.
  • B. Vozha River
    The Vozha River is a waterway in western Russia historically notable as the site of a major 14th-century battle between the Grand Duchy of Moscow and the Golden Horde.
  • C. Vasyugan River
    The Vasyugan River is a significant waterway in southwestern Siberia, Russia, known for draining vast swampy lowlands before joining the Ob River.
  • D. Votka River
    The Votka River is a smaller watercourse in Russia that feeds into the larger Kama River within the Volga basin.
  • E. Votka River
    The Votka River is a minor river in Perm Krai, Russia, known as a right-bank tributary within the Siva River basin.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f9927c8190a006110c8b996e61 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4b13935908190b5269a84a3df2460 completed April 19, 2026, 10:40 a.m.
Created at: April 10, 2026, 10:22 a.m.