Triple
T3594598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkhov River |
E76105
|
entity |
| Predicate | nameInRussian |
P20560
|
FINISHED |
| Object | Волхов |
E128726
|
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: Волхов | Statement: [Volkhov River, nameInRussian, Волхов]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Волхов Context triple: [Volkhov River, nameInRussian, Волхов]
-
A.
Volkhov
chosen
Volkhov is a town in Leningrad Oblast, Russia, situated along the Volkhov River and known for its hydroelectric power station and industrial significance.
-
B.
Volzhsky
Volzhsky is a major industrial city in southwestern Russia located across the Volga River from Volgograd.
-
C.
Tikhvin
Tikhvin is a historic town in northwestern Russia known for its ancient monastery, religious icons, and role as a regional cultural and industrial center.
-
D.
Tver River Port
Tver River Port is a river transport hub and passenger terminal in the city of Tver, Russia, serving traffic on the Volga and connecting regional waterways.
-
E.
Kholmogory
Kholmogory is a historic Russian town in the Arkhangelsk region that served as an important early northern trading and administrative center.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15d3e308190b8352ef1f054f9c3 |
completed | March 8, 2026, 6:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b44efeacf481908dd9a26f348f9977 |
completed | March 13, 2026, 5:53 p.m. |
Created at: March 8, 2026, 3:22 p.m.