Triple
T21470631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Never |
E529721
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Bolshoy Never River |
—
|
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: Bolshoy Never River | Statement: [Never, locatedOn, Bolshoy Never River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bolshoy Never River Context triple: [Never, locatedOn, Bolshoy Never River]
-
A.
Bolshoy Never River
chosen
The Bolshoy Never River is a watercourse in Russia’s Amur Oblast that serves as a geographic feature near the town of Skovorodino in the Russian Far East.
-
B.
Bolshoy Kinel River
The Bolshoy Kinel River is a tributary watercourse in Russia that feeds into the larger Samara River system.
-
C.
Bolshaya Kaksha River
The Bolshaya Kaksha River is a lesser-known Russian watercourse that serves as a tributary within the Vetluga River basin.
-
D.
Norilskaya River
The Norilskaya River is a river in northern Siberia, Russia, flowing near the industrial city of Norilsk in the Krasnoyarsk Krai region.
-
E.
Bolshoy Ik River
The Bolshoy Ik River is a tributary watercourse in Russia that feeds into the larger Sakmara River system.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea13adfc819093324ae6fe66c3fd |
completed | April 23, 2026, 9:44 a.m. |
Created at: April 16, 2026, 6:17 p.m.