Triple
T11981307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Yalu River |
E285165
|
entity |
| Predicate | commander |
P1061
|
FINISHED |
| Object | Liu Buchan |
E280664
|
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: Liu Buchan | Statement: [Battle of the Yalu River, commander, Liu Buchan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Liu Buchan Context triple: [Battle of the Yalu River, commander, Liu Buchan]
-
A.
Liu Buchan
chosen
Liu Buchan was a late Qing dynasty Chinese naval officer best known for commanding the Beiyang Fleet during the First Sino-Japanese War.
-
B.
Zhao Bingjun
Zhao Bingjun was an early Republican Chinese politician who served as a key government leader during the formative years of the Republic of China.
-
C.
Lu Chaoyang
Lu Chaoyang is a prominent Chinese physicist known for his contributions to quantum information science and quantum optics.
-
D.
Zhu Zhanyong
Zhu Zhanyong was a Ming dynasty imperial prince, known primarily as a son of the Hongxi Emperor of China.
-
E.
Kang Sheng
Kang Sheng was a prominent Chinese Communist Party leader and chief of Mao Zedong’s secret police, notorious for his role in political purges and the Cultural Revolution.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90395a8788190bfbb3506c29e3825 |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65e94b6008190ae19c245c4c62b5e |
completed | May 2, 2026, 8:29 p.m. |
Created at: April 8, 2026, 9:46 p.m.