Triple

T10928563
Position Surface form Disambiguated ID Type / Status
Subject Pripyat River E258137 entity
Predicate hasTributary P415 FINISHED
Object Horyn River E418475 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: Horyn River | Statement: [Pripyat River, hasTributary, Horyn River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horyn River
Context triple: [Pripyat River, hasTributary, Horyn River]
  • A. Horyn River chosen
    The Horyn River is a major Eastern European waterway flowing through Ukraine and Belarus, forming part of the Polesia region’s extensive river network.
  • B. Arys River
    The Arys River is a significant watercourse in southern Kazakhstan that flows through the Turkistan region before joining the Syr Darya.
  • C. Tynda River
    The Tynda River is a tributary of the Zeya River in Russia’s Amur Oblast, known for flowing through the town of Tynda in the Russian Far East.
  • D. Vytegra River
    The Vytegra River is a waterway in northwestern Russia that connects Lake Onega to Lake Ladoga and forms an important segment of the Volga–Baltic navigation system.
  • E. Zergan River
    The Zergan River is a tributary watercourse in the Middle East that feeds into the Khabur River, contributing to the hydrology of the upper Euphrates basin.
  • 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_69d6aa864ed88190818280ab6791d065 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7709da23c819096f4bba1cd4ff5cb completed April 9, 2026, 9:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69f12f646ec88190ab4745c52798b599 completed April 28, 2026, 10:06 p.m.
Created at: April 8, 2026, 9:22 p.m.