Triple

T9055125
Position Surface form Disambiguated ID Type / Status
Subject Gilaks E216977 entity
Predicate primaryLanguage P238 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: [Gilaks, primaryLanguage, Gilaki language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gilaki language
Context triple: [Gilaks, primaryLanguage, 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_69ca83d4425481909a319dab847724ec completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc7a7488188190b3dd6bc2f2377503 completed April 1, 2026, 1:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0178be518819080bd6c8cf0a737e8 completed April 3, 2026, 7:39 p.m.
Created at: March 30, 2026, 7:10 p.m.