Triple
T18753901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 林 |
E458596
|
entity |
| Predicate | bopomofo |
P52966
|
FINISHED |
| Object | ㄌㄧㄣˊ |
—
|
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: ㄌㄧㄣˊ | Statement: [林, bopomofo, ㄌㄧㄣˊ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bopomofo Context triple: [林, bopomofo, ㄌㄧㄣˊ]
-
A.
mandarinReadingBopomofo
chosen
Indicates the Bopomofo (Zhuyin) phonetic transcription used to represent the Mandarin pronunciation of a given expression or character.
-
B.
ChinesePinyin
Indicates that one entity is the Chinese pinyin (romanized phonetic transcription) representation of another entity.
-
C.
mandarinTone
Indicates the specific tonal pattern in Mandarin Chinese with which an entity (such as a syllable or word) is pronounced.
-
D.
cantoneseJyutping
Indicates that an entity’s name or term is represented using the Cantonese Jyutping romanization system.
-
E.
usesLogogramsFrom
Indicates that one writing system or notation incorporates or employs logographic characters originating from another system.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ef4ee48190a9892ac9787ffe37 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.