Triple
T655211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myanmar |
E11632
|
entity |
| Predicate | ethnicGroup |
P194
|
FINISHED |
| Object | Shan |
E56815
|
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: Shan | Statement: [Myanmar, ethnicGroup, Shan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shan Context triple: [Myanmar, ethnicGroup, Shan]
-
A.
Shan
chosen
The Shan are a Tai ethnic group primarily inhabiting Myanmar's Shan State, known for their distinct language, Buddhist traditions, and historical Shan principalities.
-
B.
Shina
Shina is an Indo-Aryan language spoken primarily in the Gilgit-Baltistan region of Pakistan and surrounding Himalayan areas.
-
C.
Shimsha
Shimsha is a river in southern India that flows through Karnataka and is known for its waterfalls and contribution to the Kaveri river system.
-
D.
Shi
Shi is a Chinese surname historically associated with members of the Jewish community in Kaifeng, China.
-
E.
Chun
Chun is the given name of Peng Chun Chang, a prominent Chinese philosopher and diplomat who helped draft the Universal Declaration of Human Rights.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4d57688190a9515ac494a97b22 |
completed | March 1, 2026, 8:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a637452b0c8190a1e82989f20e68db |
completed | March 3, 2026, 1:20 a.m. |
Created at: March 1, 2026, 7:36 p.m.