Triple
T23194959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lin Zexu |
E579848
|
entity |
| Predicate | courtesyName |
P570
|
FINISHED |
| Object | Yuanfu |
—
|
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: Yuanfu | Statement: [Lin Zexu, courtesyName, Yuanfu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yuanfu Context triple: [Lin Zexu, courtesyName, Yuanfu]
-
A.
Yuanfu
chosen
Yuanfu was the courtesy name of Lin Zexu, the prominent Qing dynasty official known for his role in suppressing the opium trade and helping trigger the First Opium War.
-
B.
Fuyuan
Fuyuan is a county-level city in northeastern Heilongjiang Province, China, located near the confluence of the Heilong (Amur) and Wusuli (Ussuri) rivers and known as one of the country’s easternmost settlements.
-
C.
Yuanzhen
Yuanzhen was the Chinese era name used during the reign of Temür Khan, the second emperor of the Yuan dynasty.
-
D.
Jingyu
Jingyu is a Chinese given name that can be used for people of any gender and carries various meanings depending on the characters used to write it.
-
E.
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.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fda64cc8190aeb5ccd8d8d20858 |
completed | April 29, 2026, 4:58 a.m. |
Created at: April 17, 2026, 4:06 p.m.