Triple
T3420729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burmese |
E72108
|
entity |
| Predicate | writingSystemUsage |
P26603
|
FINISHED |
| Object | used in government |
—
|
LITERAL 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: used in government | Statement: [Burmese, writingSystemUsage, used in government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemUsage Context triple: [Burmese, writingSystemUsage, used in government]
-
A.
writingSystemUsedIn
chosen
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
B.
writingSystemUsedSince
Indicates that a particular writing system has been in use starting from a specified point in time or period.
-
C.
writingSystemStatus
Indicates the current functional or sociolinguistic state of a writing system, such as whether it is actively used, obsolete, official, or endangered.
-
D.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
E.
writingSystemScope
Indicates the range or extent of content, languages, or contexts to which a particular writing system applies or is used.
- F. None of above.
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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94eb9e8819087a525df4550914b |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.