Triple

T9051926
Position Surface form Disambiguated ID Type / Status
Subject Palaung language E216903 entity
Predicate hasDialect P4251 FINISHED
Object Rumai Palaung E775524 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: Rumai Palaung | Statement: [Palaung language, hasDialect, Rumai Palaung]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rumai Palaung
Context triple: [Palaung language, hasDialect, Rumai Palaung]
  • A. Ruching Palaung chosen
    Ruching Palaung is a regional dialect of the Palaung language spoken by Palaung communities in parts of mainland Southeast Asia.
  • B. Lengpui
    Lengpui is a town in the Indian state of Mizoram known primarily for hosting the region’s main airport serving the capital city, Aizawl.
  • C. Ba Maw
    Ba Maw was a Burmese nationalist leader and politician who served as the head of state of Japanese-occupied Burma during World War II.
  • D. Mongpan
    Mongpan is a historic Shan principality in what is now Myanmar, known as one of the traditional Shan States.
  • E. Kawthaung
    Kawthaung is a coastal town in southern Myanmar that serves as a key gateway for cross-border trade and travel with Thailand.
  • 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_69ca83d362e88190ae44b4e4dc194209 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc7a700de48190aa9f61d850e01cbd completed April 1, 2026, 1:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69cffdbd54848190ba79d873321f4fc9 completed April 3, 2026, 5:49 p.m.
Created at: March 30, 2026, 7:10 p.m.