Triple
T18599796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yong Pung How |
E454588
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Yong |
—
|
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: Yong | Statement: [Yong Pung How, familyName, Yong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yong Context triple: [Yong Pung How, familyName, Yong]
-
A.
Yong
Yong was the personal given name of Emperor Shizong, a prominent ruler of the Jurchen-led Jin dynasty in 12th-century China.
-
B.
Yong
chosen
Yong is a variant transliteration of the Chinese surname and given name commonly romanized as Yang.
-
C.
Yong
Yong was an ancient Chinese city that served as the political and administrative center of the Qin state during the Warring States period.
-
D.
Yong
Yong was the personal name of King Wuling of Zhao, a reformist ruler of the Warring States period in ancient China known for adopting nomadic military tactics and attire.
-
E.
Onjong
Onjong is a town in North Korea notable as the site of early major engagements during the Chinese First Phase Offensive in the Korean War.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5475018548190a2f497081af7ce55 |
completed | April 19, 2026, 9:21 p.m. |
Created at: April 10, 2026, 11:45 a.m.