Triple

T7660924
Position Surface form Disambiguated ID Type / Status
Subject Gondi–Kui subgroup E173502 entity
Predicate hasMember P10 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: [Gondi–Kui subgroup, hasMember, Koya language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koya language
Context triple: [Gondi–Kui subgroup, hasMember, 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. Koyra Senni language
    The Koyra Senni language is a Songhay language spoken primarily along the Niger River in Mali, notably around the city of Gao.
  • C. Kioko language
    The Kioko language is an Austronesian language of the Muna–Buton subgroup spoken by a small community in southeastern Sulawesi, Indonesia.
  • D. Miyako language
    The Miyako language is a Southern Ryukyuan language of Japan’s Okinawa Prefecture, spoken primarily on the Miyako Islands and noted for its distinct phonology and endangered status.
  • E. Yakoma language
    The Yakoma language is a Ubangian language spoken by the Yakoma people of the Central African Republic and neighboring regions.
  • 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_69c69955517c819085bc715b96d304d2 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c701a47a5c8190867e39f552c86787 completed March 27, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69c89b14b6848190892a262903d78b79 completed March 29, 2026, 3:23 a.m.
Created at: March 27, 2026, 3:59 p.m.