Triple

T13957242
Position Surface form Disambiguated ID Type / Status
Subject Aliabad E335696 entity
Predicate localLanguage P1252 FINISHED
Object Burushaski E85247 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: Burushaski | Statement: [Aliabad, localLanguage, Burushaski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burushaski
Context triple: [Aliabad, localLanguage, Burushaski]
  • A. Burushaski chosen
    Burushaski is a language isolate spoken by the Burusho people in northern Pakistan, particularly in the Hunza, Nagar, and Yasin valleys of Gilgit-Baltistan.
  • B. Brahui
    Brahui is a Dravidian language spoken primarily by the Brahui people in parts of Pakistan, Afghanistan, and Iran.
  • C. Mundari
    The Mundari are a Nilotic ethnic group of South Sudan known for their cattle-herding culture and pastoralist lifestyle.
  • D. Mundari
    Mundari is an Austroasiatic Munda language of eastern India, spoken primarily by the Munda people in states such as Jharkhand, Odisha, and West Bengal.
  • E. 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.
  • 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_69d81c61f3508190aaf2ca0dc0002c59 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e7a34f08190aa0d88b66154f268 completed April 14, 2026, 12:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69fba1d27a0c8190b5d95ea86fc1a420 completed May 6, 2026, 8:17 p.m.
Created at: April 9, 2026, 10:17 p.m.