Triple

T7916473
Position Surface form Disambiguated ID Type / Status
Subject Central Dravidian languages E183839 entity
Predicate includes P1393 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: [Central Dravidian languages, includes, Koya language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koya language
Context triple: [Central Dravidian languages, includes, 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_69ca828efbe48190bd48482650182e79 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a76ae688190b068e4c92603a16d completed March 31, 2026, 3:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5be54fdc81909a988114a6f30a13 completed March 31, 2026, 5:30 a.m.
Created at: March 30, 2026, 5:05 p.m.