Triple
T5755451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhuang language |
E126954
|
entity |
| Predicate | writingReform |
P45284
|
FINISHED |
| Object | Latin-based orthography introduced in 1957 |
—
|
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: Latin-based orthography introduced in 1957 | Statement: [Zhuang language, writingReform, Latin-based orthography introduced in 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingReform Context triple: [Zhuang language, writingReform, Latin-based orthography introduced in 1957]
-
A.
writingForm
Indicates the specific script, notation, or written representation used to express a piece of language or content.
-
B.
languageReform
chosen
Indicates efforts or actions aimed at changing, standardizing, or improving aspects of a language, such as its spelling, grammar, or usage rules.
-
C.
writtenForm
Indicates that one entity is the textual or orthographic representation (spelling or written version) of another entity.
-
D.
rite
Indicates a ceremonial or ritual action performed according to established traditions or religious practices.
-
E.
writingTool
Indicates that one entity serves as a tool or instrument used by another entity for the act of writing.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02906848c8190bf7b0d62f57c27fa |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.