Triple
T2781736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izhora River |
E61711
|
entity |
| Predicate | hasLeftTributary |
P415
|
FINISHED |
| Object | Tosna River |
E61943
|
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: Tosna River | Statement: [Izhora River, hasLeftTributary, Tosna River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tosna River Context triple: [Izhora River, hasLeftTributary, Tosna River]
-
A.
Tosna River
chosen
The Tosna River is a waterway in northwestern Russia that flows through the Leningrad Oblast before joining the Neva River.
-
B.
Luga River
The Luga River is a significant waterway in northwestern Russia that flows through Novgorod and Leningrad Oblasts before emptying into the Gulf of Finland in the Baltic Sea.
-
C.
Izhora River
The Izhora River is a small river in northwestern Russia that flows through the Leningrad Oblast and Saint Petersburg region before joining the Neva River.
-
D.
Snezhnaya River
The Snezhnaya River is a Siberian river in Russia that serves as one of the tributaries feeding into Lake Baikal.
-
E.
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.
- 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_69ab4b7e43c48190997b8fc8fb1663ab |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd9b88888190ab021afbaf3aa3c0 |
completed | March 7, 2026, 8:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b53fc6f4b48190aebcf7457b6d670d |
completed | March 14, 2026, 11 a.m. |
Created at: March 6, 2026, 9:57 p.m.