Triple

T4753153
Position Surface form Disambiguated ID Type / Status
Subject Gonds E105524 entity
Predicate languageSpoken P151 FINISHED
Object Gondi language E144000 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: Gondi language | Statement: [Gonds, languageSpoken, Gondi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gondi language
Context triple: [Gonds, languageSpoken, Gondi language]
  • A. Gondi language chosen
    The Gondi language is a Dravidian language spoken by the indigenous Gond people of central India, written in multiple scripts including Telugu and Devanagari.
  • B. Gonja language
    The Gonja language is a Gur language spoken primarily by the Gonja people in northern Ghana.
  • C. Chimariko language
    The Chimariko language is an extinct Native American language once spoken in northwestern California, often classified within the proposed Hokan language family.
  • D. Mandar language
    Mandar is an Austronesian language spoken primarily by the Mandar people along the western coast of Sulawesi in Indonesia.
  • E. Kharia language
    Kharia language is a Munda language spoken primarily by the Kharia people in eastern India, especially in the states of Jharkhand, Odisha, and Chhattisgarh.
  • 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_69bd43f07fa48190954317d01600994a completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64e72d1c81908eb60960751e52b1 completed March 20, 2026, 3:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a6600e481909c3fb1decf23d7d8 completed March 21, 2026, 6:27 a.m.
Created at: March 20, 2026, 1:20 p.m.