Triple
T28269420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 蔣 |
E712801
|
entity |
| Predicate | transliterationInVietnameseSinoVietnamese |
P188777
|
FINISHED |
| Object | Tưởng |
—
|
NE NERFINISHED |
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: Tưởng | Statement: [蔣, transliterationInVietnameseSinoVietnamese, Tưởng]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transliterationInVietnameseSinoVietnamese Context triple: [蔣, transliterationInVietnameseSinoVietnamese, Tưởng]
-
A.
equivalentInVietnameseChuNom
Indicates that one entity is the equivalent representation of another entity in the Vietnamese Chữ Nôm writing system.
-
B.
ChinesePinyin
Indicates that one entity is the Chinese pinyin (romanized phonetic transcription) representation of another entity.
-
C.
formerTransliteration
Indicates that one transliteration was previously used for an entity but has since been replaced by a different transliteration.
-
D.
mandarinReadingBopomofo
Indicates the Bopomofo (Zhuyin) phonetic transcription used to represent the Mandarin pronunciation of a given expression or character.
-
E.
WadeGilesForm
Indicates that one entity is the Wade–Giles romanized form corresponding to another entity’s written or spoken Chinese form.
- F. None of above. chosen
Provenance (4 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_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbad1b3ba08190ad69e21461333f2e |
completed | May 6, 2026, 9:05 p.m. |
Created at: April 27, 2026, 11:17 p.m.