Triple
T36905218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chow Shiu-hung |
E912751
|
entity |
| Predicate | nameInChineseRomanization |
P164578
|
FINISHED |
| Object | Chow Shiu-hung |
—
|
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: Chow Shiu-hung | Statement: [Chow Shiu-hung, nameInChineseRomanization, Chow Shiu-hung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInChineseRomanization Context triple: [Chow Shiu-hung, nameInChineseRomanization, Chow Shiu-hung]
-
A.
nameInLanguageRomanization
chosen
Indicates that an entity’s name is represented in the romanized (Latin-script) form of a particular language.
-
B.
nameInChinese
Indicates that an entity has a specific written name or label expressed in the Chinese language.
-
C.
nameInMcCuneReischauer
Indicates that an entity’s name is represented using the McCune–Reischauer romanization system.
-
D.
nameOrderInChinese
Indicates that the entities are arranged in the order that personal names are written or spoken in Chinese (family name first, given name second).
-
E.
surnameRomanization
Indicates that one entity is the romanized (Latin-alphabet) form of another entity's surname.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdaa04908190ad7535c5f06f4b69 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.