Triple

T19677388
Position Surface form Disambiguated ID Type / Status
Subject Shina language E472489 entity
Predicate neighboringLanguages P16383 FINISHED
Object Burushaski 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: Burushaski | Statement: [Shina language, neighboringLanguages, Burushaski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burushaski
Context triple: [Shina language, neighboringLanguages, 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. Chazhashi
    Chazhashi is a historic village in Georgia’s Svaneti region, renowned for its medieval stone towers and traditional mountain architecture.
  • D. Mundari
    The Mundari are a Nilotic ethnic group of South Sudan known for their cattle-herding culture and pastoralist lifestyle.
  • E. 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.
  • 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_69d8e514f2e08190ba70a4449519d218 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e641bceef881909c5b655af709c8c6 completed April 20, 2026, 3:09 p.m.
Created at: April 10, 2026, 1:45 p.m.