Triple

T22652579
Position Surface form Disambiguated ID Type / Status
Subject Achomi people E559131 entity
Predicate ethnonym P4709 FINISHED
Object Achomi NE NERFINISHED

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: Achomi | Statement: [Achomi people, ethnonym, Achomi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Achomi
Context triple: [Achomi people, ethnonym, Achomi]
  • A. Achomi people chosen
    The Achomi people are an Iranian ethnic group primarily from southern Iran and parts of the Persian Gulf region, known for their distinct Achomi language and cultural traditions.
  • B. Achomi language
    Achomi language is a Southwestern Iranian language spoken primarily by the Achomi people in southern Iran and parts of the Persian Gulf region.
  • C. Kurmanji
    Kurmanji is the most widely spoken dialect of the Kurdish language, used primarily by Kurds across Turkey, Syria, Iraq, Iran, and the diaspora.
  • D. Talysh
    The Talysh are an Iranian ethnic group primarily inhabiting the southwestern coast of the Caspian Sea in northern Iran and southeastern Azerbaijan, with their own distinct Talysh language and cultural traditions.
  • E. Gilaki
    Gilaki is an Iranian language spoken primarily in Iran’s Gilan Province along the Caspian Sea coast.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245489dd88190b1f674acf61c8769 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1703d7d648190aafe275cd04c47cf completed April 29, 2026, 2:43 a.m.
Created at: April 17, 2026, 3:06 p.m.