Triple

T10611396
Position Surface form Disambiguated ID Type / Status
Subject Sagaing E276015 entity
Predicate hasNearbyCity P350 FINISHED
Object Shwebo E778448 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: Shwebo | Statement: [Sagaing, hasNearbyCity, Shwebo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shwebo
Context triple: [Sagaing, hasNearbyCity, Shwebo]
  • A. Shwebo chosen
    Shwebo is a historic city in central Myanmar best known as the birthplace and early royal seat of King Alaungpaya, founder of the Konbaung Dynasty.
  • B. Thayarwady
    Thayarwady is a town in central Myanmar known as an administrative and commercial center within the Bago Region.
  • C. Thandwe
    Thandwe is a coastal town in western Myanmar’s Rakhine State, historically known as Sandoway and serving as an important regional center near the popular Ngapali Beach.
  • D. Wagaung
    Wagaung is the fifth month of the traditional Burmese lunisolar calendar, typically falling around August in the Gregorian calendar.
  • E. Ta’ang
    Ta’ang is a Mon–Khmer language spoken primarily by the Ta’ang (Palaung) ethnic group in parts of Myanmar and neighboring regions.
  • 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_69d6aaf948d88190806cc3a8c47a3fb2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d6df5a1450819082ad445712fb7868 completed April 8, 2026, 11:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69d95ec61b388190adee9b3577567709 completed April 10, 2026, 8:34 p.m.
Created at: April 8, 2026, 7:33 p.m.