Triple
T9174407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bomdila |
E220159
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Monpa language |
E769464
|
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: Monpa language | Statement: [Bomdila, languageSpoken, Monpa language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Monpa language Context triple: [Bomdila, languageSpoken, Monpa language]
-
A.
Monpa language
chosen
The Monpa language is a Tibeto-Burman language spoken by the Monpa people of Arunachal Pradesh in northeastern India and adjacent regions of Tibet.
-
B.
Nyishi language
The Nyishi language is a Tani (Tibeto-Burman) language spoken primarily by the Nyishi people of Arunachal Pradesh in northeastern India.
-
C.
Mampruli language
Mampruli is a Gur language spoken primarily by the Mamprusi people in northern Ghana and parts of neighboring West African countries.
-
D.
Munji language
The Munji language is an Eastern Iranian language spoken by the Munji people in Afghanistan’s remote Munjan Valley, closely related to the Yidgha language of Pakistan.
-
E.
Yamphu language
The Yamphu language is a Kiranti Sino-Tibetan language spoken by the Yamphu ethnic community in eastern Nepal.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa2f9708190a955bf28a4f04004 |
completed | April 1, 2026, 6:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d054a36ef881908079558050c67e7c |
completed | April 4, 2026, midnight |
Created at: March 30, 2026, 7:23 p.m.