Triple
T16412166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Aizong of Jin |
E398592
|
entity |
| Predicate | personalName |
P24312
|
FINISHED |
| Object | Wanyan Shouxu |
E1080061
|
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: Wanyan Shouxu | Statement: [Emperor Aizong of Jin, personalName, Wanyan Shouxu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wanyan Shouxu Context triple: [Emperor Aizong of Jin, personalName, Wanyan Shouxu]
-
A.
Wanyan Shouxu
chosen
Wanyan Shouxu was a Jin dynasty military leader who played a significant command role during the Mongol–Jin War in early 13th-century China.
-
B.
Wanyan Zonggan
Wanyan Zonggan was a Jurchen prince of the Jin dynasty and the son of Emperor Xizong of Jin.
-
C.
Wanyan Yunji
Wanyan Yunji was a prince of the Jurchen-led Jin dynasty in China, known primarily as the son of Emperor Zhangzong of Jin.
-
D.
Wanyan Dan
Wanyan Dan, better known by his temple name Emperor Xizong of Jin, was a 12th-century emperor of the Jurchen-led Jin dynasty in northern China.
-
E.
Wanyan Xiyin
Wanyan Xiyin was a prominent Jurchen statesman and scholar of the Jin dynasty best known for devising the Jurchen script used to write the Jurchen language.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32874a0cc8190874aea10b1d13004 |
completed | April 18, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006071a8ac8190b004a2861343960a |
completed | May 10, 2026, 10:39 a.m. |
Created at: April 10, 2026, 5:09 a.m.