Triple
T13706476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tedim Chin |
E328653
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Zomi language |
E575828
|
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: Zomi language | Statement: [Tedim Chin, hasAlternativeName, Zomi language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zomi language Context triple: [Tedim Chin, hasAlternativeName, Zomi language]
-
A.
Nyishi language
The Nyishi language is a Tani (Tibeto-Burman) language spoken primarily by the Nyishi people of Arunachal Pradesh in northeastern India.
-
B.
Karbi language
The Karbi language is a Tibeto-Burman language spoken primarily by the Karbi people in Northeast India, especially in Assam.
-
C.
Mizo language
chosen
Mizo language is a Tibeto-Burman language spoken primarily in the Indian state of Mizoram and surrounding regions by the Mizo people.
-
D.
Pa’O language
The Pa’O language is a Tibeto-Burman language spoken primarily by the Pa’O (Taungthu) people of Myanmar, especially in Shan and Kayin States.
-
E.
Zeliang language
The Zeliang language is a Tibeto-Burman language spoken by the Zeliang Naga people of Northeast India, primarily in parts of Nagaland and Manipur.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad17732c8190bbd0d73107711c99 |
completed | April 13, 2026, 8:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7945b63288190819621830ac1c0d6 |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:54 p.m.