Triple

T14883205
Position Surface form Disambiguated ID Type / Status
Subject Yandabo E350051 entity
Predicate hasNearbyMajorCity P1982 FINISHED
Object Mandalay E57185 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: Mandalay | Statement: [Yandabo, hasNearbyMajorCity, Mandalay]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mandalay
Context triple: [Yandabo, hasNearbyMajorCity, Mandalay]
  • A. Mandalay chosen
    Mandalay is a major cultural and economic center in central Myanmar, historically known as the last royal capital of the Burmese kingdom.
  • B. Yangon
    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.
  • 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. Pathein
    Pathein is a major city in Myanmar’s Ayeyarwady Region, known as a regional commercial hub and for its traditional handcrafted umbrellas.
  • 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_69d822ee4f408190b6ac3b2fa434f0df completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded5e7c0e48190af2d68a71130585c completed April 15, 2026, 12:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe9687a5888190a6e6ffd781f64edc completed May 9, 2026, 2:05 a.m.
Created at: April 10, 2026, 1:56 a.m.