Triple
T12664670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Votkinsk |
E302516
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Votka River |
E332793
|
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: Votka River | Statement: [Votkinsk, locatedOn, Votka River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Votka River Context triple: [Votkinsk, locatedOn, Votka River]
-
A.
Votka River
chosen
The Votka River is a smaller watercourse in Russia that feeds into the larger Kama River within the Volga basin.
-
B.
Vasyugan River
The Vasyugan River is a significant waterway in southwestern Siberia, Russia, known for draining vast swampy lowlands before joining the Ob River.
-
C.
Vokhma River
The Vokhma River is a smaller watercourse in Russia that serves as one of the tributaries feeding into the larger Vetluga River system.
-
D.
Kastornaya River
The Kastornaya River is a waterway in western Russia that flows through the settlement of Kastornoye and forms part of the region’s local river system.
-
E.
Vetluga River
The Vetluga River is a significant waterway in western Russia that flows through several regions 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617e030881908444743b8a7e0d75 |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c6f404888190b7bb47bff1a7c1e1 |
completed | May 3, 2026, 10:06 p.m. |
Created at: April 9, 2026, 5:19 p.m.