Triple

T7660831
Position Surface form Disambiguated ID Type / Status
Subject Kolami E173499 entity
Predicate hasDialects P4251 FINISHED
Object Southeastern 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: Southeastern Kolami | Statement: [Kolami, hasDialects, Southeastern Kolami]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Southeastern Kolami
Context triple: [Kolami, hasDialects, Southeastern 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. Nagpuri
    Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
  • C. Khasi language
    Khasi language is an Austroasiatic language spoken primarily in the northeastern Indian state of Meghalaya by the Khasi people.
  • D. Dholuo
    Dholuo is a Nilotic language spoken primarily by the Luo people of western Kenya and parts of Tanzania.
  • E. Burushaski
    Burushaski is a language isolate spoken by the Burusho people in northern Pakistan, particularly in the Hunza, Nagar, and Yasin valleys of Gilgit-Baltistan.
  • 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_69c69955517c819085bc715b96d304d2 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c701a47a5c8190867e39f552c86787 completed March 27, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8a2206664819085c6825e63eadd6f completed March 29, 2026, 3:53 a.m.
Created at: March 27, 2026, 3:59 p.m.