Triple
T11806441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanintharyi Region |
E280756
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Kawthaung |
E177836
|
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: Kawthaung | Statement: [Tanintharyi Region, hasPort, Kawthaung]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kawthaung Context triple: [Tanintharyi Region, hasPort, Kawthaung]
-
A.
Kawthaung
chosen
Kawthaung is a coastal town in southern Myanmar that serves as a key gateway for cross-border trade and travel with Thailand.
-
B.
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.
-
C.
Myingyan
Myingyan is a town in central Myanmar known as a commercial and transport hub along the Irrawaddy River in the Mandalay Region.
-
D.
Mawlamyine
Mawlamyine is a coastal city in southeastern Myanmar and the capital of Mon State, known historically as an important port and cultural center.
-
E.
Thabeikkyin
Thabeikkyin is a town in central Myanmar situated along the Ayeyarwady River within the country’s Mandalay Region.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5c8324481909a54852a9bb714e0 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f43f9e99788190a5a8abb135426038 |
completed | May 1, 2026, 5:52 a.m. |
Created at: April 8, 2026, 9:42 p.m.