Triple
T28269391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 蔣 |
E712801
|
entity |
| Predicate | CantonesePronunciationJyutping |
P52960
|
FINISHED |
| Object | zoeng2 |
—
|
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: zoeng2 | Statement: [蔣, CantonesePronunciationJyutping, zoeng2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CantonesePronunciationJyutping Context triple: [蔣, CantonesePronunciationJyutping, zoeng2]
-
A.
cantoneseJyutping
chosen
Indicates that an entity’s name or term is represented using the Cantonese Jyutping romanization system.
-
B.
cantoneseYaleForm
Indicates the written form of a term using the Yale romanization system for Cantonese pronunciation.
-
C.
ChinesePinyin
Indicates that one entity is the Chinese pinyin (romanized phonetic transcription) representation of another entity.
-
D.
mandarinReadingBopomofo
Indicates the Bopomofo (Zhuyin) phonetic transcription used to represent the Mandarin pronunciation of a given expression or character.
-
E.
cantoneseForm
Indicates that one entity is the Cantonese-language form or representation of another entity.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6441fa00c819092afb06beb9fb252 |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:16 p.m.