Triple

T1522193
Position Surface form Disambiguated ID Type / Status
Subject Maung E32253 entity
Predicate languageOfOrigin P151 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: [Maung, languageOfOrigin, Burmese language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burmese language
Context triple: [Maung, languageOfOrigin, 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. Chakma language
    The Chakma language is an Indo-Aryan language spoken primarily by the Chakma people of Bangladesh and northeastern India.
  • E. Burmese calendar
    The Burmese calendar is a traditional lunisolar calendar used in Myanmar to determine religious festivals, cultural events, and historical dates.
  • 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_69a885e9b0ac819093a9806ad0efc82c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a907fe8b0c8190a765afd3a10ee5e0 completed March 5, 2026, 4:35 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad294f9e2481909f1d685d7f083c6a completed March 8, 2026, 7:46 a.m.
Created at: March 4, 2026, 7:26 p.m.