Triple

T1392874
Position Surface form Disambiguated ID Type / Status
Subject Baloch people E30599 entity
Predicate ethnonym P4709 FINISHED
Object Baluchi E14427 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: Baluchi | Statement: [Baloch people, ethnonym, Baluchi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baluchi
Context triple: [Baloch people, ethnonym, Baluchi]
  • A. Balochi chosen
    Balochi is an Iranian language spoken primarily by the Baloch people across Pakistan, Iran, and Afghanistan, with several dialects and a rich oral literary tradition.
  • B. Zazaki
    Zazaki is an Indo-Iranian language spoken primarily in eastern Turkey, often associated with the Zaza people and considered one of the main Kurdish-related dialects or languages.
  • C. Gorani
    Gorani is a Northwestern Iranian language variety traditionally spoken by Kurdish communities in parts of Iran and Iraq, notable for its rich literary and religious heritage.
  • D. Khowar
    Khowar is an Indo-Aryan language primarily spoken in the Chitral region of Pakistan and parts of neighboring areas, known for its rich oral tradition and distinct phonology.
  • 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 (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_69a498fd4e408190bd73eca30ea9754c completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c360a7f08190ab7e903764b06fdf completed March 1, 2026, 10:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad0156109081908f163af94e4e7978 completed March 8, 2026, 4:55 a.m.
Created at: March 1, 2026, 7:59 p.m.