Triple

T17364258
Position Surface form Disambiguated ID Type / Status
Subject Toliš E422146 entity
Predicate refersTo P37 FINISHED
Object Talysh language NE ONNED1

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: Talysh language | Statement: [Toliš, refersTo, Talysh language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Talysh language
Context triple: [Toliš, refersTo, Talysh 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. Dameli language
    The Dameli language is an Indo-Aryan (Dardic) language spoken by a small community in the Damel Valley of Chitral District in northern Pakistan.
  • C. Talysh chosen
    The Talysh are an Iranian ethnic group primarily inhabiting the southwestern coast of the Caspian Sea in northern Iran and southeastern Azerbaijan, with their own distinct Talysh language and cultural traditions.
  • D. Achomi language
    Achomi language is a Southwestern Iranian language spoken primarily by the Achomi people in southern Iran and parts of the Persian Gulf region.
  • E. Lezgian
    Lezgian is a Northeast Caucasian language spoken primarily by the Lezgin people in southern Dagestan and northern Azerbaijan.
  • 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_69d889d6535c81908be333c01deaec4e completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a4f52988190847230e119a35b87 completed April 19, 2026, 2:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01956294ec819083c1dde8fc2685e4 in_progress May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:44 a.m.