Triple
T14061958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoelun |
E338367
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Temüge |
E1105617
|
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: Temüge | Statement: [Hoelun, child, Temüge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Temüge Context triple: [Hoelun, child, Temüge]
-
A.
Temüge
chosen
Temüge was a son of the Mongol chieftain Yesügei and a younger brother of Genghis Khan, known for his role within the early Mongol imperial family.
-
B.
Temüjin
Temüjin is the birth name of Genghis Khan, the founder and first Great Khan of the Mongol Empire.
-
C.
Yesün Temür
Yesün Temür was a 14th-century Mongol ruler who served as Great Khan of the Mongol Empire and emperor of the Yuan dynasty in China.
-
D.
Yuanzong
Yuanzong is the courtesy name of Sun Hao, the last emperor of Eastern Wu during China’s Three Kingdoms period.
-
E.
Toghon Temür
Toghon Temür was the last emperor of the Yuan dynasty in China, whose troubled reign ended with the dynasty’s collapse and the rise of the Ming.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568876308190840361dcaf10bd45 |
completed | April 14, 2026, 3 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd949b9fc481908c7717c412e05fac |
completed | May 8, 2026, 7:45 a.m. |
Created at: April 9, 2026, 10:21 p.m.