Triple

T715770
Position Surface form Disambiguated ID Type / Status
Subject Moskva River E14309 entity
Predicate connectedTo P37 FINISHED
Object Volga River E9405 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: Volga River | Statement: [Moskva River, connectedTo, Volga River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Volga River
Context triple: [Moskva River, connectedTo, Volga River]
  • A. Volga River chosen
    The Volga River is the longest river in Europe, flowing through central Russia to the Caspian Sea and serving as a vital waterway for transport, industry, and culture.
  • B. Ural River
    The Ural River is a major river in Russia and Kazakhstan that traditionally marks part of the boundary between the European and Asian continents.
  • C. Kuban River
    The Kuban River is a major river in the North Caucasus region of Russia that flows through the Krasnodar Krai before emptying into the Sea of Azov.
  • D. Lena River
    The Lena River is one of the longest rivers in the world, flowing through Siberia in northeastern Russia to the Arctic Ocean.
  • E. Samara River
    The Samara River is a significant river in European Russia that flows through the Samara region before joining the Volga River.
  • 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_69a4934a36e081909e7abef98b898a4e completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a574b4d881908b6d0be386081efd completed March 1, 2026, 8:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69a673329a0c8190b725b9863ba4c162 completed March 3, 2026, 5:35 a.m.
Created at: March 1, 2026, 7:37 p.m.