Triple
T12833219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Yenisei |
E306838
|
entity |
| Predicate | languageOfName |
P15
|
FINISHED |
| Object | Tuvan |
E233990
|
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: Tuvan | Statement: [Little Yenisei, languageOfName, Tuvan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tuvan Context triple: [Little Yenisei, languageOfName, Tuvan]
-
A.
Tuvan
chosen
Tuvan is a Turkic language spoken primarily in the Tuva Republic of Russia, known for its rich oral traditions and association with Tuvan throat singing.
-
B.
Ussuriysk
Ussuriysk is a city in Russia’s Far East known as an important regional transport and economic center near the border with China.
-
C.
Bashkir
Bashkir is a Turkic language spoken primarily by the Bashkir people in Russia’s Republic of Bashkortostan and surrounding regions.
-
D.
Kalmyk
Kalmyk refers to a Mongolic ethnic group primarily living in Russia’s Kalmykia region, known for being the only traditionally Buddhist people in Europe.
-
E.
Kalmyk language
Kalmyk language is a Mongolic language spoken primarily by the Kalmyk people in Russia’s Republic of Kalmykia, notable as the only traditionally Buddhist region in Europe.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96fb0bb208190bdc4d3dc7909be06 |
completed | April 10, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b9bb0b48190ba3f9f92d270db83 |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:34 p.m.