Triple
T15459510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dong Biwu |
E371859
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 董必武 |
E450560
|
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: 董必武 | Statement: [Dong Biwu, nativeName, 董必武]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 董必武 Context triple: [Dong Biwu, nativeName, 董必武]
-
A.
何叔衡
何叔衡 was a Chinese revolutionary and one of the early leaders and co-founders of the Communist Party of China.
-
B.
周恩来
周恩来是中华人民共和国的开国总理和重要外交家，被视为中国现代史上最具影响力的政治家之一。
-
C.
汪兆铭
汪兆铭 was a prominent Chinese politician and early associate of Sun Yat-sen who later became infamous for leading the Japanese-backed collaborationist regime in Nanjing during World War II.
-
D.
叶剑英
叶剑英 was a prominent Chinese Communist military leader and statesman who served as one of the Ten Marshals of the People’s Republic of China and later as its top legislator.
-
E.
Dong Biwu
chosen
Dong Biwu was a prominent Chinese Communist revolutionary and politician who served as one of the vice chairmen of the People's Republic of China and a key leader in the early PRC government.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1623f0819086f6fc2bfd536609 |
completed | April 16, 2026, 1:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff21b9817c819082e5c571b08bafb5 |
completed | May 9, 2026, 11:59 a.m. |
Created at: April 10, 2026, 3:32 a.m.