Triple
T14315838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Li Yuanhong |
E354953
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Yuanhong |
E354953
|
NE 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: Yuanhong | Statement: [Li Yuanhong, givenName, Yuanhong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yuanhong Context triple: [Li Yuanhong, givenName, Yuanhong]
-
A.
Yuanhong
chosen
Yuanhong is a Chinese given name that appears in the full name of the historical figure Li Yuanhong.
-
B.
Yuanxin
Yuanxin is the given name of Mao Yuanxin, a Chinese political figure known for being the nephew of Mao Zedong and a prominent youth leader during the Cultural Revolution.
-
C.
Xingyuan
Xingyuan was the Chinese era name used during part of Emperor Dezong of Tang’s reign in the late eighth century.
-
D.
Zhenyuan
Zhenyuan was a late 19th-century Chinese ironclad battleship of the Beiyang Fleet that played a prominent role in the First Sino-Japanese War.
-
E.
Zhenyuan
Zhenyuan was a regnal era of the Tang dynasty marked by Emperor Dezong’s efforts to stabilize imperial authority and restore central control after periods of rebellion and fragmentation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8838e45c819080ee69dd39e3bd43 |
completed | April 14, 2026, 6:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4687c6bc819088452892128c420e |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:12 a.m.