Triple
T28075555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hán |
E709529
|
entity |
| Predicate | pinyinSystem |
P41705
|
FINISHED |
| Object | Hanyu Pinyin |
—
|
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: Hanyu Pinyin | Statement: [Hán, pinyinSystem, Hanyu Pinyin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pinyinSystem Context triple: [Hán, pinyinSystem, Hanyu Pinyin]
-
A.
ChinesePinyin
Indicates that one entity is the Chinese pinyin (romanized phonetic transcription) representation of another entity.
-
B.
usesPhoneticSystem
chosen
Indicates that one entity employs or is based on a particular phonetic system for representing or encoding sounds.
-
C.
mandarinReadingBopomofo
Indicates the Bopomofo (Zhuyin) phonetic transcription used to represent the Mandarin pronunciation of a given expression or character.
-
D.
cantoneseJyutping
Indicates that an entity’s name or term is represented using the Cantonese Jyutping romanization system.
-
E.
cangjieInput
Indicates the mapping from a character to its corresponding Cangjie input code used for text entry.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6403f29d481909168f09c19dcbb18 |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:48 p.m.