Triple
T9051651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palaungic |
E216897
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Wa language |
E220623
|
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: Wa language | Statement: [Palaungic, hasLanguage, Wa language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wa language Context triple: [Palaungic, hasLanguage, Wa language]
-
A.
Wa language
chosen
The Wa language is a Mon–Khmer language spoken primarily by the Wa people in parts of Myanmar and China.
-
B.
Wab language
The Wab language is a lesser-known Papuan language spoken by an indigenous community in Papua New Guinea.
-
C.
Waja language
The Waja language is a lesser-known Niger-Congo language spoken by the Waja people of northeastern Nigeria.
-
D.
Zaiwa language
The Zaiwa language is a Tibeto-Burman language spoken primarily by the Zaiwa people in parts of Yunnan, China and northern Myanmar.
-
E.
Ao language
Ao language is a Sino-Tibetan language spoken primarily by the Ao Naga people in Nagaland, India.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a700de48190aa9f61d850e01cbd |
completed | April 1, 2026, 1:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfebc90bf88190bbcdab07ca93f569 |
completed | April 3, 2026, 4:33 p.m. |
Created at: March 30, 2026, 7:10 p.m.