Triple

T4147935
Position Surface form Disambiguated ID Type / Status
Subject Tamil script E89832 entity
Predicate usedFor P98 FINISHED
Object Irula language E202767 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: Irula language | Statement: [Tamil script, usedFor, Irula language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Irula language
Context triple: [Tamil script, usedFor, Irula language]
  • A. Irula language chosen
    Irula language is a Dravidian tribal language spoken primarily by the Irula people in parts of Tamil Nadu and Kerala in southern India.
  • B. 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.
  • C. Chenchu language
    The Chenchu language is a Dravidian tribal language spoken by the Chenchu people of India, primarily in the forests of Andhra Pradesh and Telangana.
  • D. 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.
  • E. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • 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_69aed95a59a881909b26e70b42c6811a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af026130bc8190ae3b0e9bec5ccad6 completed March 9, 2026, 5:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f3136c48190b158142311bfbc6d completed March 14, 2026, 3:30 p.m.
Created at: March 9, 2026, 3:43 p.m.