Triple

T19410176
Position Surface form Disambiguated ID Type / Status
Subject Kuvi language E485565 entity
Predicate hasAlternativeName P39 FINISHED
Object Kuvi NE NERFINISHED

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 | Statement: [Kuvi language, hasAlternativeName, Kuvi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuvi
Context triple: [Kuvi language, hasAlternativeName, Kuvi]
  • A. Kuvi chosen
    Kuvi is a Dravidian language spoken primarily by the Kuvi tribal communities in parts of Odisha and Andhra Pradesh in India.
  • B. Kuuvak
    Kuuvak is the traditional Indigenous name, used by local Iñupiat peoples, for the river known in English as the Kobuk River in northwestern Alaska.
  • C. Kuenn
    Kuenn is a surname most notably associated with Harvey Kuenn, an American Major League Baseball player and manager.
  • D. Ku
    Ku is a principal Hawaiian god associated with war, politics, and prosperity, widely venerated in traditional Native Hawaiian religion.
  • E. Kuci
    Kuci is the historical name of Kuqa, an ancient oasis town and important Buddhist cultural center along the Silk Road in what is now Xinjiang, China.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62af4cc0c81909056b5e2ee574ab1 completed April 20, 2026, 1:32 p.m.
Created at: April 10, 2026, 1:37 p.m.