Triple
T19839694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fu Bingchang |
E476692
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Bingchang |
—
|
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: Bingchang | Statement: [Fu Bingchang, givenName, Bingchang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bingchang Context triple: [Fu Bingchang, givenName, Bingchang]
-
A.
Bingchang
chosen
Bingchang is a Chinese given name, notably borne by diplomat and politician Fu Bingchang.
-
B.
Yingchang
Yingchang was a city in northern China that served as a retreat and final refuge for the last Yuan emperor, Toghon Temür, after the dynasty’s collapse.
-
C.
Binglin
Binglin is the given name of Zhang Taiyan, a prominent Chinese philologist, revolutionary, and influential thinker of the late Qing and early Republican era.
-
D.
Bocheng
Bocheng is a Chinese given name most notably borne by the prominent Communist military leader and strategist Liu Bocheng.
-
E.
Dayong
Dayong is the former name of the city now known as Zhangjiajie in Hunan Province, China, famed for its dramatic sandstone pillar landscapes.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65804be608190b49e110c3bf381bc |
completed | April 20, 2026, 4:44 p.m. |
Created at: April 10, 2026, 1:50 p.m.