Triple
T12870584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thanbyuzayat |
E307838
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Mawlamyine |
E402287
|
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: Mawlamyine | Statement: [Thanbyuzayat, near, Mawlamyine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mawlamyine Context triple: [Thanbyuzayat, near, Mawlamyine]
-
A.
Mawlamyine
chosen
Mawlamyine is a coastal city in southeastern Myanmar and the capital of Mon State, known historically as an important port and cultural center.
-
B.
Myingyan
Myingyan is a town in central Myanmar known as a commercial and transport hub along the Irrawaddy River in the Mandalay Region.
-
C.
Nyaungshwe
Nyaungshwe is a popular lakeside town in Myanmar that serves as the main gateway and tourist hub for visiting Inle Lake in Shan State.
-
D.
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.
-
E.
Kawthaung
Kawthaung is a coastal town in southern Myanmar that serves as a key gateway for cross-border trade and travel with Thailand.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d970905784819091631161a9de98c5 |
completed | April 10, 2026, 9:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8ccee708190bb4caa604386e3a3 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 5:38 p.m.