Triple
T16165120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Xizong of Jin |
E392283
|
entity |
| Predicate | reignName |
P32785
|
FINISHED |
| Object | Tianjuan |
E1195502
|
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: Tianjuan | Statement: [Emperor Xizong of Jin, reignName, Tianjuan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tianjuan Context triple: [Emperor Xizong of Jin, reignName, Tianjuan]
-
A.
Tianjuan
chosen
Tianjuan was a historical Chinese era name used during the reign of Emperor Taizong of the Jurchen-led Jin dynasty.
-
B.
Yingtian
Yingtian was an important early Ming dynasty capital city, historically centered around present-day Nanjing in China.
-
C.
Jingyu
Jingyu is a Chinese given name that can be used for people of any gender and carries various meanings depending on the characters used to write it.
-
D.
Huangtong
Huangtong was an era name used during the reign of Emperor Xizong of the Jurchen-led Jin dynasty in China.
-
E.
Yujian
Yujian was the personal name of the Longwu Emperor, a short-lived Ming dynasty claimant who resisted the Qing conquest in southern 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb2a25c819095437b25e6ab83f3 |
completed | April 17, 2026, 11:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000785fcd481909ddf92cf9cc5c0aa |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 5:02 a.m.