Triple

T8013083
Position Surface form Disambiguated ID Type / Status
Subject Mae Sot District E186543 entity
Predicate capital P234 FINISHED
Object Mae Sot E32257 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: Mae Sot | Statement: [Mae Sot District, capital, Mae Sot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mae Sot
Context triple: [Mae Sot District, capital, Mae Sot]
  • A. Mae Sot chosen
    Mae Sot is a Thai border town in Tak Province known as a major hub for cross-border trade and migration with Myanmar and for its numerous refugee and humanitarian aid organizations.
  • B. Thongduang
    Thongduang was the birth name of King Rama I of Siam, the founder and first monarch of Thailand’s Chakri Dynasty.
  • C. Lao Phra Lak Phra Lam
    Lao Phra Lak Phra Lam is the Lao national epic, a localized adaptation of the Indian Ramayana that reflects Lao culture, religion, and literary tradition.
  • D. Tonsawang
    Tonsawang is an Austronesian language spoken by the Tonsawang people in North Sulawesi, Indonesia.
  • E. Tasiwit
    Tasiwit is an alternative name for Siwi, a Berber language spoken in Egypt’s Siwa Oasis.
  • 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_69ca82abaffc8190ab8af79cdbc31ab3 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3d73bf048190ad8066a7e95c34b0 completed March 31, 2026, 3:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc63c1f76881909ad6d7777090f2e2 completed April 1, 2026, 12:16 a.m.
Created at: March 30, 2026, 5:19 p.m.