Triple
T12137268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ding Ruchang |
E289090
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ruchang |
E289090
|
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: Ruchang | Statement: [Ding Ruchang, givenName, Ruchang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ruchang Context triple: [Ding Ruchang, givenName, Ruchang]
-
A.
Ruchang
chosen
Ruchang is a Chinese given name most notably borne by Ding Ruchang, a late Qing dynasty naval commander.
-
B.
Hucheng
Hucheng is the given name of Yang Hucheng, a prominent Chinese general and political figure best known for his role in the Xi'an Incident of 1936.
-
C.
Yongcheng
Yongcheng was a Qing dynasty imperial prince, known as one of the sons of the Qianlong Emperor of China.
-
D.
Luzhi
Luzhi is an ancient canal town near Suzhou in China, renowned for its well-preserved waterways, stone bridges, and traditional Jiangnan architecture.
-
E.
Yuanxing
Yuanxing was the era name used by Eastern Wu emperor Sun Hao during part of his tumultuous late Three Kingdoms–period reign in China.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9158dd00c819082651891898b91bb |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e4a573c8190b5dd6cc61849739b |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:49 p.m.