Triple

T2873234
Position Surface form Disambiguated ID Type / Status
Subject Arakan E56814 entity
Predicate hasLanguage P15 FINISHED
Object Burmese language E72108 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: Burmese language | Statement: [Arakan, hasLanguage, Burmese language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burmese language
Context triple: [Arakan, hasLanguage, Burmese language]
  • A. Burmese chosen
    Burmese is the official Sino-Tibetan language of Myanmar, spoken by the majority Bamar ethnic group and used widely in government, education, and media.
  • B. Rohingya language
    The Rohingya language is an Eastern Indo-Aryan language spoken primarily by the Rohingya people from Rakhine State in Myanmar and neighboring regions.
  • C. Burmese script
    The Burmese script is an abugida used for writing the Burmese language and several other languages of Myanmar, characterized by its rounded letters and Indic origins.
  • D. Palaung language
    The Palaung language is an Austroasiatic language spoken primarily by the Palaung people in parts of Myanmar, China, and Thailand.
  • E. Pa’O language
    The Pa’O language is a Tibeto-Burman language spoken primarily by the Pa’O (Taungthu) people of Myanmar, especially in Shan and Kayin 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_69ab4a4ced288190ab6d3e062d10f7f6 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abdfe59ef88190b8bdfdd03e8965f3 completed March 7, 2026, 8:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69b01db40e388190a208fe58e2ed6029 completed March 10, 2026, 1:33 p.m.
Created at: March 6, 2026, 10:03 p.m.