Triple

T19332902
Position Surface form Disambiguated ID Type / Status
Subject Dargwa E483539 entity
Predicate hasDialects P4251 FINISHED
Object Urakhi dialect 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: Urakhi dialect | Statement: [Dargwa, hasDialects, Urakhi dialect]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Urakhi dialect
Context triple: [Dargwa, hasDialects, Urakhi dialect]
  • A. Nankani dialect
    The Nankani dialect is a regional variety of the Gur-language cluster spoken in northern Ghana and southern Burkina Faso, associated with the Nankani people.
  • B. Ushguli dialect
    The Ushguli dialect is a regional variety of the Svan language spoken in and around the highland village community of Ushguli in northwestern Georgia.
  • C. Akusha dialect chosen
    The Akusha dialect is a principal standardized variety of the Dargin language spoken in Dagestan, Russia.
  • D. Nohurli dialect
    The Nohurli dialect is a regional variety of Turkmen spoken by the Nohur people in parts of Turkmenistan, distinguished by its unique phonetic and lexical features.
  • E. Harauti dialect
    The Harauti dialect is an Indo-Aryan variety spoken primarily in the Hadoti (Harauti) region of Rajasthan and neighboring areas of India.
  • 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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e61642f49c81909226cfd701f7c139 completed April 20, 2026, 12:04 p.m.
Created at: April 10, 2026, 1:33 p.m.