Triple

T2294572
Position Surface form Disambiguated ID Type / Status
Subject Proto-Dravidian E51580 entity
Predicate ancestorOf P369 FINISHED
Object Kolami E173499 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: Kolami | Statement: [Proto-Dravidian, ancestorOf, Kolami]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kolami
Context triple: [Proto-Dravidian, ancestorOf, Kolami]
  • A. Kolami chosen
    Kolami is a Dravidian language spoken primarily by the Kolam tribal communities in central India, especially in parts of Maharashtra and Telangana.
  • B. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • C. Mundari
    Mundari is an Austroasiatic Munda language of eastern India, spoken primarily by the Munda people in states such as Jharkhand, Odisha, and West Bengal.
  • D. Bagheli
    Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
  • E. Bagri
    Bagri is an Indo-Aryan language variety spoken primarily in parts of Rajasthan, Haryana, and Punjab, often considered a dialect of Rajasthani.
  • 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_69a88b09c644819090b503456d96bf70 completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abc5da667881909186adf23a2bd45b completed March 7, 2026, 6:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae7f2654e4819090dea196cf38652e completed March 9, 2026, 8:04 a.m.
Created at: March 4, 2026, 7:49 p.m.