Triple
T20899312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khakas language |
E514627
|
entity |
| Predicate | hasDialects |
P4251
|
FINISHED |
| Object | Sagaysky dialect |
—
|
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: Sagaysky dialect | Statement: [Khakas language, hasDialects, Sagaysky dialect]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sagaysky dialect Context triple: [Khakas language, hasDialects, Sagaysky dialect]
-
A.
Sagaysky dialect
chosen
The Sagaysky dialect is a regional variety of the Khakas language spoken by the Sagay subgroup of the Khakas people in Siberia.
-
B.
Kamenskoye dialect
The Kamenskoye dialect is a regional variety of the Koryak language traditionally spoken by Koryak communities in the Kamenskoye area of Russia’s Far East.
-
C.
Kachinsky dialect
The Kachinsky dialect is a regional variety of the Khakas language spoken by Khakas communities in parts of Siberia.
-
D.
Vitskhi dialect
The Vitskhi dialect is a regional variety of the Lak language spoken by the Lak people of Dagestan in the North Caucasus.
-
E.
Itsarinsky dialect
The Itsarinsky dialect is a variety of the Dargin language spoken by the inhabitants of the village of Itsari in Dagestan, Russia.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8f92bd88190b59b2131ad1d9aa1 |
completed | April 21, 2026, 3:03 a.m. |
Created at: April 16, 2026, 12:47 p.m.