Triple
T15078801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vokhma River |
E380079
|
entity |
| Predicate | hasMouthIn |
P1008
|
FINISHED |
| Object | Vetluga River system |
E56437
|
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: Vetluga River system | Statement: [Vokhma River, hasMouthIn, Vetluga River system]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vetluga River system Context triple: [Vokhma River, hasMouthIn, Vetluga River system]
-
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.
Supin River
The Supin River is a Himalayan river in Uttarakhand, India, known for flowing through the Har Ki Doon valley before joining the Tons River.
-
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.
Valerik River
The Valerik River is a waterway in the North Caucasus region of Russia, historically noted as a site of 19th-century conflicts during the Caucasian War.
-
E.
Sidorovskaya River
The Sidorovskaya River is a significant tributary watercourse in western Siberia that feeds into Russia’s Taz River system.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fe5a208190823900b25e298dab |
completed | April 15, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae13f76881908485b3507b380799 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:03 a.m.