Triple
T5470435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buynaksk |
E122817
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Dargin |
E111143
|
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: Dargin | Statement: [Buynaksk, hasLanguage, Dargin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dargin Context triple: [Buynaksk, hasLanguage, Dargin]
-
A.
Dargin
chosen
Dargin is a Northeast Caucasian language spoken primarily by the Dargin people in the Republic of Dagestan in Russia.
-
B.
Lezgian
Lezgian is a Northeast Caucasian language spoken primarily by the Lezgin people in southern Dagestan and northern Azerbaijan.
-
C.
Gagauz
The Gagauz are a Turkic-speaking Orthodox Christian ethnic group primarily living in Moldova and neighboring regions of Eastern Europe.
-
D.
Gorani
Gorani is a Northwestern Iranian language variety traditionally spoken by Kurdish communities in parts of Iran and Iraq, notable for its rich literary and religious heritage.
-
E.
Kumyk
Kumyk is a Turkic language traditionally spoken by the Kumyk people in the North Caucasus region, particularly in present-day Dagestan, Russia.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd921b65f48190af7fcf89140f9ba8 |
completed | March 20, 2026, 6:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf4893029081908a801c7a44872ebf |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:09 p.m.