Triple
T10748566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putao |
E253514
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Burmese |
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 | Statement: [Putao, languageSpoken, Burmese]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burmese Context triple: [Putao, languageSpoken, Burmese]
-
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.
Lolo-Burmese
Lolo-Burmese is a major branch of the Sino-Tibetan language family that includes Burmese and numerous related languages spoken primarily in Myanmar and southwestern China.
-
C.
Birman
Birman is a surname most notably associated with Joan S. Birman, an American mathematician recognized for her work in topology and braid theory.
-
D.
Chinese Burmese
Chinese Burmese are an ethnic group in Myanmar descended from Chinese migrants, blending Chinese heritage with Burmese culture and society.
-
E.
Intha Burmese
Intha Burmese is a regional variety of the Burmese language spoken primarily by the Intha people around Inle Lake in Myanmar.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71dbecd58819081e859ebf72f656c |
completed | April 9, 2026, 3:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de231af7388190b73347a3ffc1077a |
completed | April 14, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:15 p.m.