Triple

T5961818
Position Surface form Disambiguated ID Type / Status
Subject Achomi language E132654 entity
Predicate alternativeName P39 FINISHED
Object Larestani Achomi E132654 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: Larestani Achomi | Statement: [Achomi language, alternativeName, Larestani Achomi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Larestani Achomi
Context triple: [Achomi language, alternativeName, Larestani Achomi]
  • A. Bakhtiari Luri
    Bakhtiari Luri is a major Southwestern Iranian dialect spoken primarily by the Bakhtiari people of western and southwestern Iran.
  • B. Mazanderani language
    Mazanderani language is a Northwestern Iranian language spoken primarily along Iran’s southern Caspian Sea coast, especially in Mazandaran Province.
  • C. Achomi language chosen
    Achomi language is a Southwestern Iranian language spoken primarily by the Achomi people in southern Iran and parts of the Persian Gulf region.
  • D. Gilaki
    Gilaki is an Iranian language spoken primarily in Iran’s Gilan Province along the Caspian Sea coast.
  • 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_69c0086c2364819091e9fe2f58fa2517 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c039ff421c819085fc92f0b707d31b completed March 22, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11ccdec948190a0792c351a6867b7 completed March 23, 2026, 10:58 a.m.
Created at: March 22, 2026, 4:02 p.m.