Triple

T8401398
Position Surface form Disambiguated ID Type / Status
Subject Edward River E198379 entity
Predicate flowsThrough P225 FINISHED
Object Moulamein E684809 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: Moulamein | Statement: [Edward River, flowsThrough, Moulamein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moulamein
Context triple: [Edward River, flowsThrough, Moulamein]
  • A. Moulamein chosen
    Moulamein is a small rural town in the Riverina region of New South Wales, Australia, known for its historic buildings and riverside setting.
  • 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. 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.
  • 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. 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_69ca8310df9c8190b25f16161cca3e41 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cb824da3148190bfa3a1abfdfa02de completed March 31, 2026, 8:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69cde8789a608190a3503f544a19d204 completed April 2, 2026, 3:54 a.m.
Created at: March 30, 2026, 6:04 p.m.