Triple

T3913904
Position Surface form Disambiguated ID Type / Status
Subject Kurukh E88788 entity
Predicate nativeName P15 FINISHED
Object Kurukh 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 | Statement: [Kurukh, nativeName, Kurukh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kurukh
Context triple: [Kurukh, nativeName, Kurukh]
  • A. Kurukh chosen
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • 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. 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.
  • D. Kolami
    Kolami is a Dravidian language spoken primarily by the Kolam tribal communities in central India, especially in parts of Maharashtra and Telangana.
  • E. Tulu
    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.
  • 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_69aed955229881909e85e73ffab1d343 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeed38e2808190acbd0a7a3b677798 completed March 9, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5285c52808190b9cbb2e3e03a18cb completed March 14, 2026, 9:20 a.m.
Created at: March 9, 2026, 3:22 p.m.