Triple
T3133993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kostroma |
E65483
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Kostroma River |
E361030
|
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: Kostroma River | Statement: [Kostroma, locatedOn, Kostroma River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kostroma River Context triple: [Kostroma, locatedOn, Kostroma River]
-
A.
Kostroma River
chosen
The Kostroma River is a major waterway in central Russia that flows through Kostroma Oblast before joining the Volga River.
-
B.
Vyatka River
The Vyatka River is a major river in western Russia that flows through the Kirov and Nizhny Novgorod regions and plays an important role in regional transport, ecology, and settlement.
-
C.
Votka River
The Votka River is a smaller watercourse in Russia that feeds into the larger Kama River within the Volga basin.
-
D.
Sheksna River
The Sheksna River is a significant waterway in northwestern Russia that forms part of the Volga–Baltic Waterway, connecting the Volga River basin with the Baltic Sea.
-
E.
Snezhnaya River
The Snezhnaya River is a Siberian river in Russia that serves as one of the tributaries feeding into Lake Baikal.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada562540081908627950dd0b56a1e |
completed | March 8, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b595d57bcc8190b2a6e28437a32b93 |
completed | March 14, 2026, 5:07 p.m. |
Created at: March 8, 2026, 3:05 p.m.