Triple
T1822726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manipur |
E40576
|
entity |
| Predicate | officialLanguage |
P236
|
FINISHED |
| Object | Meitei |
E133169
|
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: Meitei | Statement: [Manipur, officialLanguage, Meitei]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Meitei Context triple: [Manipur, officialLanguage, Meitei]
-
A.
Meitei language
chosen
Meitei language is the principal Tibeto-Burman language of the Indian state of Manipur, serving as its official and most widely spoken tongue.
-
B.
Meitei people
The Meitei people are an ethnic group native to the Indian state of Manipur, known for their distinct culture, martial traditions, and classical dance and music forms.
-
C.
Assamese
Assamese is an Eastern Indo-Aryan language primarily spoken in the Indian state of Assam and recognized as one of the official languages of India.
-
D.
Chakma language
The Chakma language is an Indo-Aryan language spoken primarily by the Chakma people of Bangladesh and northeastern India.
-
E.
Burushaski
Burushaski is a language isolate spoken by the Burusho people in northern Pakistan, particularly in the Hunza, Nagar, and Yasin valleys of Gilgit-Baltistan.
- 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_69a8864526c081908a3a4d74f689e2c5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa662d13e88190a22b0faf0d848c7d |
completed | March 6, 2026, 5:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adbf6722f081908c5368a09d1507ac |
completed | March 8, 2026, 6:26 p.m. |
Created at: March 4, 2026, 7:32 p.m.