Triple
T21961107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temür Khan |
E542328
|
entity |
| Predicate | reignName |
P32785
|
FINISHED |
| Object | Yuanzhen |
—
|
NE NERFINISHED |
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: Yuanzhen | Statement: [Temür Khan, reignName, Yuanzhen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yuanzhen Context triple: [Temür Khan, reignName, Yuanzhen]
-
A.
Yuanzhen
chosen
Yuanzhen was the Chinese era name used during the reign of Temür Khan, the second emperor of the Yuan dynasty.
-
B.
Jianzhong
Jianzhong was a brief imperial era name used during the reign of Emperor Dezong in the Tang dynasty, marking a specific period in his rule.
-
C.
Xingyuan
Xingyuan was the Chinese era name used during part of Emperor Dezong of Tang’s reign in the late eighth century.
-
D.
Zhenyuan
Zhenyuan was a late 19th-century Chinese ironclad battleship of the Beiyang Fleet that played a prominent role in the First Sino-Japanese War.
-
E.
Zhenyuan
Zhenyuan was a regnal era of the Tang dynasty marked by Emperor Dezong’s efforts to stabilize imperial authority and restore central control after periods of rebellion and fragmentation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12455e99c819092ec59fe571f814e |
completed | April 28, 2026, 9:19 p.m. |
Created at: April 16, 2026, 8 p.m.