Triple

T20104951
Position Surface form Disambiguated ID Type / Status
Subject Malvi people E490143 entity
Predicate language P15 FINISHED
Object Malvi language 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: Malvi language | Statement: [Malvi people, language, Malvi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Malvi language
Context triple: [Malvi people, language, Malvi language]
  • A. Malvi language chosen
    Malvi language is an Indo-Aryan language spoken primarily in the Malwa region of central India, closely related to Nimadi and other Rajasthani dialects.
  • B. Malvani language
    Malvani language is an Indo-Aryan dialect closely related to Konkani and Marathi, spoken primarily in the Malvan region of Maharashtra and parts of Goa in India.
  • C. Malgana language
    The Malgana language is an Aboriginal Australian language traditionally spoken by the Malgana people of Western Australia’s Shark Bay region.
  • D. Kumaoni language
    Kumaoni language is an Indo-Aryan language of the Central Pahari group spoken primarily in the Kumaon region of Uttarakhand, India.
  • E. Dhatki language
    Dhatki language is an Indo-Aryan language spoken primarily by the Thari people in the Thar Desert region spanning parts of Pakistan and India.
  • 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_69da62636cc08190982cc71733a17b8d completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e666daf73c819089f02ca6faa2c283 completed April 20, 2026, 5:48 p.m.
Created at: April 11, 2026, 11:28 p.m.