Triple

T3754931
Position Surface form Disambiguated ID Type / Status
Subject Naypyidaw E82022 entity
Predicate predecessorCapital P3417 FINISHED
Object Yangon E42684 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: Yangon | Statement: [Naypyidaw, predecessorCapital, Yangon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yangon
Context triple: [Naypyidaw, predecessorCapital, Yangon]
  • A. Yangon chosen
    Yangon is Myanmar’s largest city and former capital, known as a major commercial hub featuring a mix of colonial architecture and prominent Buddhist landmarks like the Shwedagon Pagoda.
  • B. Mandalay
    Mandalay is a major cultural and economic center in central Myanmar, historically known as the last royal capital of the Burmese kingdom.
  • C. 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.
  • D. Taunggyi
    Taunggyi is a major city in eastern Myanmar known as an administrative, cultural, and commercial center in the Shan region.
  • E. 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.
  • 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_69ad8b1db40081908b61ffa6b78afd4d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcb94ffc08190a7fd1ce71a15f787 completed March 8, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4e50825588190b620950ac1d4f408 completed March 14, 2026, 4:33 a.m.
Created at: March 8, 2026, 3:35 p.m.