Triple
T5549005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temür Khan |
E145478
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Zhenjin |
E141746
|
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: Zhenjin | Statement: [Temür Khan, father, Zhenjin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zhenjin Context triple: [Temür Khan, father, Zhenjin]
-
A.
Zhenjin
chosen
Zhenjin was the designated heir and favored son of Kublai Khan, known for his Confucian education and role in the early Yuan dynasty’s administration before his premature death.
-
B.
Zhizhong
Zhizhong is a Chinese given name shared by various individuals, including historical and contemporary figures.
-
C.
Xingzhen
Xingzhen was the personal given name of Empress Dowager Cixi, the powerful de facto ruler of the late Qing dynasty in China.
-
D.
Shëngjin
Shëngjin is a coastal town and port in northwestern Albania on the Adriatic Sea, historically significant for its strategic maritime position.
-
E.
Heqing
Heqing was an era name used during the Northern Qi dynasty in imperial China to designate a specific reign period.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fe143ec8190bb67d2530c92a419 |
completed | March 22, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0282dd7408190ad762fca9ff5e04b |
completed | March 22, 2026, 5:34 p.m. |
Created at: March 22, 2026, 3:35 p.m.