Triple

T12749469
Position Surface form Disambiguated ID Type / Status
Subject Tai Khün E304691 entity
Predicate primaryRegion P1103 FINISHED
Object Kengtung E1009468 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: Kengtung | Statement: [Tai Khün, primaryRegion, Kengtung]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kengtung
Context triple: [Tai Khün, primaryRegion, Kengtung]
  • A. Kengtung chosen
    Kengtung is a historic town in eastern Myanmar’s Shan State, known as a cultural center of the Tai ethnic groups and a gateway to the Golden Triangle region.
  • B. Myitkyina
    Myitkyina is the capital of Kachin State in northern Myanmar, known as a key regional center and transport hub near the upper reaches of the Irrawaddy River.
  • C. Taunggyi
    Taunggyi is a major city in eastern Myanmar known as an administrative, cultural, and commercial center in the Shan region.
  • D. Kawthaung
    Kawthaung is a coastal town in southern Myanmar that serves as a key gateway for cross-border trade and travel with Thailand.
  • E. 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.
  • 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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96bd75f508190aaae0969f33d1523 completed April 10, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6af49d2c4819097168712af7d4c15 completed May 3, 2026, 2:13 a.m.
Created at: April 9, 2026, 5:27 p.m.