Triple
T15876359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rakhine State |
E384961
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Sittwe |
E218985
|
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: Sittwe | Statement: [Rakhine State, hasCity, Sittwe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sittwe Context triple: [Rakhine State, hasCity, Sittwe]
-
A.
Sittwe
chosen
Sittwe is a coastal city in western Myanmar that has been a focal point of political unrest and ethnic tensions, including major protests during the Saffron Revolution.
-
B.
Lashio
Lashio is a key town in northern Myanmar that historically served as an important transport and trade hub, particularly during World War II as the inland gateway to the Burma Road.
-
C.
Tharrawaddy
Tharrawaddy was a 19th-century Burmese prince who later became King of the Konbaung Dynasty in Myanmar.
-
D.
Amarapura
Amarapura is a former royal city in Myanmar renowned for its role as an early Burmese capital and for landmarks such as the U Bein Bridge.
-
E.
Buthidaung
Buthidaung is a town in Myanmar’s Rakhine State, known for its ethnically diverse population and proximity to the border with Bangladesh.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e155fdc1b881909d1c82c4c66a195a |
completed | April 16, 2026, 9:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb59ddc488190ae6b6913f85005f6 |
completed | May 9, 2026, 10:30 p.m. |
Created at: April 10, 2026, 4:51 a.m.