Triple
T11672208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhuyin |
E277409
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Bopomofo |
E277409
|
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: Bopomofo | Statement: [Zhuyin, alsoKnownAs, Bopomofo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bopomofo Context triple: [Zhuyin, alsoKnownAs, Bopomofo]
-
A.
Zhuyin
chosen
Zhuyin is a phonetic writing system for transcribing the sounds of Mandarin Chinese, primarily used in Taiwan for teaching pronunciation and literacy.
-
B.
Pe̍h-ōe-jī
Pe̍h-ōe-jī is a Latin-based orthography developed by Western missionaries for writing Southern Min (Hokkien) and related Chinese dialects.
-
C.
Hangul Jamo
Hangul Jamo is a Unicode block that encodes the individual consonant and vowel letters used to write the Korean Hangul script.
-
D.
Hanyu Pinyin
Hanyu Pinyin is the official romanization system for Standard Mandarin Chinese, using the Latin alphabet to represent Chinese pronunciation.
-
E.
Taiwanese Romanization System
The Taiwanese Romanization System is a standardized Latin-based orthography used to phonetically represent Taiwanese Hokkien.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a443b6848190a1eb6825fbc49d08 |
completed | April 10, 2026, 7:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef13d3a8608190a084d8bbcac4f924 |
completed | April 27, 2026, 7:44 a.m. |
Created at: April 8, 2026, 9:40 p.m.