Triple

T8120398
Position Surface form Disambiguated ID Type / Status
Subject Northern Iran E189591 entity
Predicate languageSpoken P151 FINISHED
Object Gilaki 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 | Statement: [Northern Iran, languageSpoken, Gilaki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gilaki
Context triple: [Northern Iran, languageSpoken, Gilaki]
  • A. Gilaki chosen
    Gilaki is an Iranian language spoken primarily in Iran’s Gilan Province along the Caspian Sea coast.
  • B. Bakhtiari Luri
    Bakhtiari Luri is a major Southwestern Iranian dialect spoken primarily by the Bakhtiari people of western and southwestern Iran.
  • C. Mazanderani language
    Mazanderani language is a Northwestern Iranian language spoken primarily along Iran’s southern Caspian Sea coast, especially in Mazandaran Province.
  • D. 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.
  • E. Central Luri
    Central Luri is a major variety of the Luri language spoken by Lur communities in western Iran, characterized by features transitional between Persian and Kurdish.
  • 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_69ca82bb74848190afb1f18640632c10 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb4359f3dc8190a2330cf6efb8c084 completed March 31, 2026, 3:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc9454ccb48190b0f894bed5da8a01 completed April 1, 2026, 3:43 a.m.
Created at: March 30, 2026, 5:33 p.m.