Triple

T9319082
Position Surface form Disambiguated ID Type / Status
Subject Palaungic languages E224199 entity
Predicate hasLanguage P15 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: [Palaungic languages, hasLanguage, Rumai Palaung]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rumai Palaung
Context triple: [Palaungic languages, hasLanguage, 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. Ta’ang
    Ta’ang is a Mon–Khmer language spoken primarily by the Ta’ang (Palaung) ethnic group in parts of Myanmar and neighboring regions.
  • E. Mongpan
    Mongpan is a historic Shan principality in what is now Myanmar, known as one of the traditional Shan States.
  • 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_69ca8426d48481909596360f7791c7dd completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd358c7d348190a10fd8670d7756f5 completed April 1, 2026, 3:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69d0c7c1fc848190bbb3ef6a1ed7a7d2 completed April 4, 2026, 8:11 a.m.
Created at: March 30, 2026, 7:38 p.m.