Triple

T19410175
Position Surface form Disambiguated ID Type / Status
Subject Kuvi language E485565 entity
Predicate hasAlternativeName P39 FINISHED
Object Kuvinga 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: Kuvinga | Statement: [Kuvi language, hasAlternativeName, Kuvinga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuvinga
Context triple: [Kuvi language, hasAlternativeName, Kuvinga]
  • A. Kuvinga chosen
    Kuvinga is an alternative name for the Kuvi language, a Dravidian language spoken by indigenous communities in eastern India.
  • B. Kuanua
    Kuanua is an Austronesian language spoken primarily by the Tolai people of East New Britain in Papua New Guinea.
  • C. Kesbewa
    Kesbewa is a suburban town in Sri Lanka’s Western Province, situated within the greater Colombo metropolitan area.
  • D. Kunkavav
    Kunkavav is a town in the Amreli district of Gujarat, India, known for its local markets and role as a regional agricultural center.
  • E. Kukawa
    Kukawa is a historic town in northeastern Nigeria that once served as the political and cultural center of the Kanuri people and the Bornu Empire.
  • 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.