Triple

T4996085
Position Surface form Disambiguated ID Type / Status
Subject Southern Gondi E112248 entity
Predicate closelyRelatedTo P37 FINISHED
Object Koya language E111783 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 language | Statement: [Southern Gondi, closelyRelatedTo, Koya language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koya language
Context triple: [Southern Gondi, closelyRelatedTo, Koya language]
  • A. Koya language chosen
    Koya language is a South-Central Dravidian language spoken by the Koya tribal communities in central and southern India.
  • B. Kioko language
    The Kioko language is an Austronesian language of the Muna–Buton subgroup spoken by a small community in southeastern Sulawesi, Indonesia.
  • C. Yakoma language
    The Yakoma language is a Ubangian language spoken by the Yakoma people of the Central African Republic and neighboring regions.
  • D. Kaado language
    The Kaado language is a regional variety within the Songhay language family spoken by communities in parts of West Africa.
  • E. Kokota language
    The Kokota language is an Austronesian language spoken by the Kokota people of Santa Isabel Island in the Solomon Islands.
  • 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_69bd4432b32c81909f3b3c6bd10f0653 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd72a0122c8190bb2fc655f3bc11b0 completed March 20, 2026, 4:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69be8a3489f08190a338de8d8be09813 completed March 21, 2026, 12:08 p.m.
Created at: March 20, 2026, 1:34 p.m.