Triple

T1472868
Position Surface form Disambiguated ID Type / Status
Subject Kurdish language E27174 entity
Predicate hasDialect P4251 FINISHED
Object Gorani E41273 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: Gorani | Statement: [Kurdish language, hasDialect, Gorani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gorani
Context triple: [Kurdish language, hasDialect, Gorani]
  • A. Gorani chosen
    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.
  • B. Zazaki
    Zazaki is an Indo-Iranian language spoken primarily in eastern Turkey, often associated with the Zaza people and considered one of the main Kurdish-related dialects or languages.
  • C. Khowar
    Khowar is an Indo-Aryan language primarily spoken in the Chitral region of Pakistan and parts of neighboring areas, known for its rich oral tradition and distinct phonology.
  • D. Brahui
    Brahui is a Dravidian language spoken primarily by the Brahui people in parts of Pakistan, Afghanistan, and Iran.
  • E. Dargin
    Dargin is a Northeast Caucasian language spoken primarily by the Dargin people in the Republic of Dagestan in 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_69a496d25d6881909dbd84f86d763992 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c5dc90e481908a4935f266bc7850 completed March 1, 2026, 11:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad1c9fb9e48190b904440cb7229c8f completed March 8, 2026, 6:52 a.m.
Created at: March 1, 2026, 8:01 p.m.