Triple
T4825620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pskov |
E107817
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Velikaya River |
E414287
|
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: Velikaya River | Statement: [Pskov, locatedOn, Velikaya River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Velikaya River Context triple: [Pskov, locatedOn, Velikaya River]
-
A.
Velikaya River
chosen
The Velikaya River is a major waterway in northwestern Russia that flows through Pskov Oblast into Lake Peipus, historically serving as an important trade and strategic route.
-
B.
Lena River
The Lena River is one of the longest rivers in the world, flowing through Siberia in northeastern Russia to the Arctic Ocean.
-
C.
Ural River
The Ural River is a major river in Russia and Kazakhstan that traditionally marks part of the boundary between the European and Asian continents.
-
D.
Kazan River
The Kazan River is a major river in the Republic of Tatarstan, Russia, flowing through the city of Kazan before emptying into the Volga River.
-
E.
Bolshaya Urta River
The Bolshaya Urta River is a smaller watercourse in Russia that serves as one of the tributaries feeding into the Samara 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6caf22308190a2048ec6acfa5af2 |
completed | March 20, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bec342e4788190ad9bb12e54b6a4ed |
completed | March 21, 2026, 4:11 p.m. |
Created at: March 20, 2026, 1:24 p.m.