Triple
T9488065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prasun |
E228812
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Prasun language |
E45675
|
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: Prasun language | Statement: [Prasun, hasLanguage, Prasun language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prasun language Context triple: [Prasun, hasLanguage, Prasun language]
-
A.
Prasun language
chosen
The Prasun language is a Nuristani language spoken by the Prasun (Vasi) people in parts of eastern Afghanistan.
-
B.
Prinmi language
The Prinmi language is a Sino-Tibetan language spoken primarily by the Pumi people of southwestern China, noted for its complex phonology and role in the Qiangic branch.
-
C.
Belhare language
The Belhare language is a Kiranti language of the Sino-Tibetan family spoken by the Belhare community in eastern Nepal.
-
D.
Padam language
Padam language is a Tani (Sino-Tibetan) language of northeastern India spoken by the Padam subgroup of the Mishing/Adi peoples of Arunachal Pradesh and Assam.
-
E.
Tipra language
Tipra language, also known as Kokborok, is a Tibeto-Burman language spoken primarily by the Tripuri people of the Indian state of Tripura and surrounding regions.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd80c443b88190968d2092a73e1ee4 |
completed | April 1, 2026, 8:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d14bfc9c9c81909ee0a70c323949bf |
completed | April 4, 2026, 5:35 p.m. |
Created at: March 30, 2026, 7:55 p.m.