Triple
T5657251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Turkic language |
E124648
|
entity |
| Predicate | ancestorOf |
P369
|
FINISHED |
| Object | Bashkir |
E218125
|
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: Bashkir | Statement: [Old Turkic language, ancestorOf, Bashkir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bashkir Context triple: [Old Turkic language, ancestorOf, Bashkir]
-
A.
Bashkir
chosen
Bashkir is a Turkic language spoken primarily by the Bashkir people in Russia’s Republic of Bashkortostan and surrounding regions.
-
B.
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.
-
C.
Komi
The Komi are a Finno-Ugric ethnic group indigenous to northern European Russia, known for their distinct Uralic language and traditional presence in regions such as the Komi Republic and surrounding areas.
-
D.
Karachay-Balkar
Karachay-Balkar is a Turkic language spoken primarily by the Karachay and Balkar peoples in the North Caucasus region of Russia.
-
E.
Chuvash
Chuvash are a Turkic ethnic group native to the Volga region of Russia, known for their distinct Chuvash language and culture.
- 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022fc54f08190aacc200be31a4256 |
completed | March 22, 2026, 5:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04d9ec1248190aff680acb4064a49 |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 3:42 p.m.