Triple

T2107584
Position Surface form Disambiguated ID Type / Status
Subject Odia script E42429 entity
Predicate usedFor P98 FINISHED
Object Kuvi language E111784 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: Kuvi language | Statement: [Odia script, usedFor, Kuvi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuvi language
Context triple: [Odia script, usedFor, Kuvi language]
  • A. Kui language chosen
    The Kui language is a South-Central Dravidian language spoken primarily by tribal communities in eastern India, especially in the state of Odisha.
  • B. Kaado language
    The Kaado language is a regional variety within the Songhay language family spoken by communities in parts of West Africa.
  • C. Kove language
    The Kove language is an Austronesian language spoken by the Kove people of New Britain in Papua New Guinea.
  • D. Kamviri language
    The Kamviri language is a Nuristani language spoken primarily by the Kam people in parts of eastern Afghanistan and neighboring regions of Pakistan.
  • E. Kavalan language
    The Kavalan language is an endangered Austronesian language of the indigenous Kavalan people of northeastern Taiwan.
  • 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_69a8871040f08190aac2e2d0ab6b47ad completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abbadf12b88190acc513d8512777b2 completed March 7, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae306e040081909334f2a70036c26e completed March 9, 2026, 2:29 a.m.
Created at: March 4, 2026, 7:43 p.m.