Triple
T5895675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desiya |
E131094
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Desiya Odia |
E24420
|
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: Desiya Odia | Statement: [Desiya, hasAlternativeName, Desiya Odia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Desiya Odia Context triple: [Desiya, hasAlternativeName, Desiya Odia]
-
A.
Bhuyan Odia
Bhuyan Odia is a regional dialect of the Odia language spoken by the Bhuyan community in parts of eastern India.
-
B.
Odissi
Odissi is a classical Indian dance form from the state of Odisha, known for its fluid torso movements, sculptural poses, and expressive storytelling rooted in Hindu temple traditions.
-
C.
Orya
Orya is the ISO 15924 script code representing the Odia script used for writing the Odia language of eastern India.
-
D.
Odishi
Odishi is the historical name for a region in western Georgia, corresponding largely to present-day Samegrelo and known for its distinct Mingrelian culture and history.
-
E.
Odia
chosen
Odia is an Indo-Aryan language spoken primarily in the Indian state of Odisha, known for its rich literary tradition and classical language status.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c036f3364c81909353f62ca483f24f |
completed | March 22, 2026, 6:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b1558fa48190a6ecde69c1477863 |
completed | March 23, 2026, 3:19 a.m. |
Created at: March 22, 2026, 3:58 p.m.