Triple
T3770881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burmese script |
E83193
|
entity |
| Predicate | writingSystemFor |
P454
|
FINISHED |
| Object | Mon language |
E216899
|
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: Mon language | Statement: [Burmese script, writingSystemFor, Mon language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mon language Context triple: [Burmese script, writingSystemFor, Mon language]
-
A.
Mon language
chosen
Mon language is an Austroasiatic language historically spoken in parts of Myanmar and Thailand, notable for its ancient literary tradition and influence on regional scripts and cultures.
-
B.
Mono language
Mono language is a Native American Uto-Aztecan language traditionally spoken by the Mono people of eastern California.
-
C.
Hoanya language
The Hoanya language is an extinct Austronesian language once spoken by the Hoanya people of western Taiwan and classified among the indigenous Formosan languages.
-
D.
Bo language
Bo language is an extinct Great Andamanese language once spoken by the Bo people of the Andaman Islands in India.
-
E.
Amuesha language
The Amuesha language, also known as Yanesha', is an Arawakan language spoken by the Yanesha' people of the central Peruvian Amazon.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc307cf8819090730b5e697bb197 |
completed | March 8, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4e5287908819084319b8dfa407635 |
completed | March 14, 2026, 4:33 a.m. |
Created at: March 8, 2026, 3:36 p.m.