Triple
T21978488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolshoy Never River |
E542771
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Skovorodino |
—
|
NE NERFINISHED |
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: Skovorodino | Statement: [Bolshoy Never River, locatedNear, Skovorodino]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skovorodino Context triple: [Bolshoy Never River, locatedNear, Skovorodino]
-
A.
Skovorodino
chosen
Skovorodino is a small town in Russia’s Far Eastern Amur Oblast, known historically as a railway junction on the Trans-Siberian Railway.
-
B.
Petrovskoye
Petrovskoye was the original Russian fortress settlement that later developed into the modern city of Makhachkala in Dagestan, Russia.
-
C.
Yuzovka
Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
-
D.
Nikolskoye
Nikolskoye is a town in northwestern Russia known as part of the Saint Petersburg metropolitan area in Leningrad Oblast.
-
E.
Nikolskoye
Nikolskoye is the main and only permanent settlement on Russia’s remote Commander Islands in the Bering Sea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248a60708190a9aa8b9b7738c261 |
completed | April 28, 2026, 9:20 p.m. |
Created at: April 16, 2026, 8:03 p.m.