Triple

T17223903
Position Surface form Disambiguated ID Type / Status
Subject Gilak people E418060 entity
Predicate language P15 FINISHED
Object Gilaki language E77850 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: Gilaki language | Statement: [Gilak people, language, Gilaki language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gilaki language
Context triple: [Gilak people, language, Gilaki language]
  • A. Gilaki chosen
    Gilaki is an Iranian language spoken primarily in Iran’s Gilan Province along the Caspian Sea coast.
  • B. Mazanderani language
    Mazanderani language is a Northwestern Iranian language spoken primarily along Iran’s southern Caspian Sea coast, especially in Mazandaran Province.
  • C. Bakhtiari Luri
    Bakhtiari Luri is a major Southwestern Iranian dialect spoken primarily by the Bakhtiari people of western and southwestern Iran.
  • D. Tabriz dialect
    Tabriz dialect is a prominent regional variety of the Azerbaijani language spoken in and around the city of Tabriz in northwestern Iran, known for its distinctive phonetic and lexical features.
  • E. Northern Luri
    Northern Luri is a major variety of the Luri language spoken by Lur communities in western Iran, distinguished by its own phonological and lexical features.
  • 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_69d886d779488190b131369541c04e7d completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42ddfe3bc8190b22cee4fc0590b74 completed April 19, 2026, 1:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0167596ab481909df59ce68c7f640e completed May 11, 2026, 5:21 a.m.
Created at: April 10, 2026, 5:38 a.m.