Triple

T12404039
Position Surface form Disambiguated ID Type / Status
Subject Oraon E296333 entity
Predicate language P15 FINISHED
Object Kurukh language E88788 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: Kurukh language | Statement: [Oraon, language, Kurukh language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kurukh language
Context triple: [Oraon, language, Kurukh language]
  • A. Kurukh chosen
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central 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. Swati language
    Swati language is a Bantu language of the Nguni group spoken primarily in Eswatini and parts of South Africa.
  • D. Tharawal language
    Tharawal language is an Australian Aboriginal language traditionally spoken by the Tharawal people of coastal New South Wales, south of Sydney.
  • E. Nilu Kurumba language
    The Nilu Kurumba language is a Dravidian tribal language spoken by the Nilu Kurumba people in parts of southern India, particularly in the Nilgiri region.
  • 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_69d6ad9f464c81909db36d7e96e34b9e completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d48f1908190918551c794f98fe3 completed April 10, 2026, 7:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69f63486d1b881908d94218d2c391123 completed May 2, 2026, 5:29 p.m.
Created at: April 8, 2026, 9:55 p.m.