Triple
T16537418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Tunguska River |
E401726
|
entity |
| Predicate | languageVariant |
P5595
|
FINISHED |
| Object | Nizhnyaya Tunguska |
E619927
|
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: Nizhnyaya Tunguska | Statement: [Lower Tunguska River, languageVariant, Nizhnyaya Tunguska]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nizhnyaya Tunguska Context triple: [Lower Tunguska River, languageVariant, Nizhnyaya Tunguska]
-
A.
Lower Tunguska
chosen
The Lower Tunguska is a major Siberian river in Russia that flows through remote taiga regions before joining the Yenisei River.
-
B.
Tungus
Tungus is an older term historically used to refer to the Evenki people and their language of Siberia.
-
C.
Tunguska River
The Tunguska River is a river in the Russian Far East that flows through the sparsely populated taiga landscapes of Khabarovsk Krai before joining larger regional waterways.
-
D.
Ozyornaya
Ozyornaya is a Moscow Metro station on the Kalininsko–Solntsevskaya Line serving the western part of the city.
-
E.
Polevskoy
Polevskoy is an industrial town in Russia’s Ural region, historically associated with copper mining and metallurgy.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34559ca948190a9eb810b9b3be079 |
completed | April 18, 2026, 8:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067aafee48190a0652fb4fac04a5b |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:15 a.m.