Triple
T16475800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurux |
E400183
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Oraon 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: Oraon Kurukh | Statement: [Kurux, hasDialect, Oraon Kurukh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oraon Kurukh Context triple: [Kurux, hasDialect, Oraon Kurukh]
-
A.
Kurukh
chosen
Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
-
B.
Santhali
Santhali is an Austroasiatic language spoken primarily by the Santal people in eastern India, Bangladesh, Nepal, and Bhutan.
-
C.
Nagpuri
Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
-
D.
Maithili
Maithili is an Indo-Aryan language spoken primarily in the eastern Indian state of Bihar and neighboring regions, with a rich literary tradition and official recognition in India.
-
E.
Bhojpuri
Bhojpuri is an Indo-Aryan language spoken primarily in eastern Uttar Pradesh, western Bihar, and parts of Nepal, with a rich folk culture and a large diaspora community.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32dd43cf88190881a5cbc80da1490 |
completed | April 18, 2026, 7:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00581c24508190b4888357828fed80 |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:13 a.m.