Triple

T15252745
Position Surface form Disambiguated ID Type / Status
Subject Nu River E364558 entity
Predicate hasMajorCityOnBank P7935 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: [Nu River, hasMajorCityOnBank, Mawlamyine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mawlamyine
Context triple: [Nu River, hasMajorCityOnBank, 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. Thandaunggyi
    Thandaunggyi is a town in southeastern Myanmar known for its cool climate, hilly terrain, and tea and coffee plantations.
  • E. 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.
  • 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_69d85a0dde7481908fc64d1e82d5d20d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e007f728648190b2c86e4528542b65 completed April 15, 2026, 9:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69fee5f390bc8190bc0180c118e1523c completed May 9, 2026, 7:44 a.m.
Created at: April 10, 2026, 3:13 a.m.