Triple

T6984307
Position Surface form Disambiguated ID Type / Status
Subject Fort Sandeman E161923 entity
Predicate hasLanguage P15 FINISHED
Object Balochi 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: Balochi | Statement: [Fort Sandeman, hasLanguage, Balochi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balochi
Context triple: [Fort Sandeman, hasLanguage, Balochi]
  • 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. Pashto language
    Pashto is an Eastern Iranian language spoken primarily in Afghanistan and Pakistan, serving as one of Afghanistan’s official languages and a key marker of Pashtun ethnic identity.
  • D. Sindhi
    Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
  • E. Saraiki
    Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • 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_69c68855dc0481909b4c7e9e9ed273db completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6db90e9108190a7aedeef1fb17eb4 completed March 27, 2026, 7:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c76a0e34288190ad2decbc18190c6b completed March 28, 2026, 5:41 a.m.
Created at: March 27, 2026, 2:31 p.m.