Triple

T5809378
Position Surface form Disambiguated ID Type / Status
Subject Koya Gondi E128827 entity
Predicate hasAlternativeName P39 FINISHED
Object Koya dialect of Gondi E144000 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: Koya dialect of Gondi | Statement: [Koya Gondi, hasAlternativeName, Koya dialect of Gondi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koya dialect of Gondi
Context triple: [Koya Gondi, hasAlternativeName, Koya dialect of Gondi]
  • A. Gondi language chosen
    The Gondi language is a Dravidian language spoken by the indigenous Gond people of central India, written in multiple scripts including Telugu and Devanagari.
  • B. Tyari dialect
    The Tyari dialect is a regional variety of Assyrian Neo-Aramaic traditionally spoken by Assyrian communities from the Tyari region in the Hakkari mountains.
  • C. Werchikwar dialect
    The Werchikwar dialect is a regional variety of the Burushaski language spoken by Burusho communities in parts of northern Pakistan.
  • D. Gonja language
    The Gonja language is a Gur language spoken primarily by the Gonja people in northern Ghana.
  • E. Malwai dialect
    The Malwai dialect is a regional variety of Punjabi primarily spoken in the Malwa region of the Indian state of Punjab.
  • 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_69c0084788848190bcf71f6bc5d71597 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02b52663c8190ab44258468d4296d completed March 22, 2026, 5:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69c098416504819089356b68fabdf737 completed March 23, 2026, 1:32 a.m.
Created at: March 22, 2026, 3:52 p.m.