Triple

T9230782
Position Surface form Disambiguated ID Type / Status
Subject Hlaing River E221808 entity
Predicate hasAlternateName P39 FINISHED
Object Hlaing E780810 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: Hlaing | Statement: [Hlaing River, hasAlternateName, Hlaing]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hlaing
Context triple: [Hlaing River, hasAlternateName, Hlaing]
  • A. 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.
  • B. Hlaing Township chosen
    Hlaing Township is a residential and commercial township in Yangon, Myanmar, known for its educational institutions and proximity to central urban areas.
  • C. Pathein
    Pathein is a major city in Myanmar’s Ayeyarwady Region, known as a regional commercial hub and for its traditional handcrafted umbrellas.
  • 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_69ca83ed628c8190bc02d641e57f097f completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccee17a2dc8190b373f78be7247f0d completed April 1, 2026, 10:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69d14bcc15508190b54acd74d4d7c911 completed April 4, 2026, 5:35 p.m.
Created at: March 30, 2026, 7:29 p.m.