Triple

T7362807
Position Surface form Disambiguated ID Type / Status
Subject Kodava E169791 entity
Predicate hasNeighbouringLanguages P16383 FINISHED
Object Tulu E86782 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: Tulu | Statement: [Kodava, hasNeighbouringLanguages, Tulu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tulu
Context triple: [Kodava, hasNeighbouringLanguages, Tulu]
  • A. Tulu chosen
    Tulu is a Dravidian language spoken primarily in the coastal regions of Karnataka and northern Kerala in southwestern India, known for its rich oral traditions and distinct cultural identity.
  • B. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • C. Ganjami
    Ganjami is a regional dialect of the Odia language spoken primarily in the Ganjam region of Odisha, India.
  • D. Mirpuri
    Mirpuri is a major dialect of the Lahnda (Western Punjabi) language, primarily spoken in the Mirpur region of Azad Kashmir and among its diaspora communities.
  • E. Nagpuri
    Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
  • 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_69c68a5ade988190885b7175f63b7534 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f15f218081909b5cc7a8cc695055 completed March 27, 2026, 9:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802b90cc081908b15e61921d15b92 completed March 28, 2026, 4:32 p.m.
Created at: March 27, 2026, 3:06 p.m.