Triple
T19789546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumyks |
E475372
|
entity |
| Predicate | nativeLanguage |
P151
|
FINISHED |
| Object | Kumyk language |
—
|
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: Kumyk language | Statement: [Kumyks, nativeLanguage, Kumyk language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kumyk language Context triple: [Kumyks, nativeLanguage, Kumyk language]
-
A.
Khinalug language
The Khinalug language is a highly endangered Northeast Caucasian language spoken by the Khinalug people in a single mountain village in northern Azerbaijan.
-
B.
Kumzari language
The Kumzari language is an endangered Southwestern Iranian language spoken primarily by the Kumzari people in the Musandam Peninsula of Oman.
-
C.
Tsakhur language
The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
-
D.
Kumyk
chosen
Kumyk is a Turkic language traditionally spoken by the Kumyk people in the North Caucasus region, particularly in present-day Dagestan, Russia.
-
E.
Chulym language
The Chulym language is a critically endangered Turkic language spoken by a small indigenous community in Siberia, 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538ae5108190b80eb7de6f445f02 |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:49 p.m.