Triple
T16129266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Güyük Khan |
E391350
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Oghul Qaimish |
E1108500
|
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: Oghul Qaimish | Statement: [Güyük Khan, spouse, Oghul Qaimish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oghul Qaimish Context triple: [Güyük Khan, spouse, Oghul Qaimish]
-
A.
Oghul Khoimish
chosen
Oghul Khoimish was a 13th-century Mongol empress and regent of the Mongol Empire, serving as the widow of Great Khan Güyük and acting ruler after his death.
-
B.
Qutuqtai Khatun
Qutuqtai Khatun was a Mongol noblewoman and consort of the Great Khan Möngke during the height of the Mongol Empire in the 13th century.
-
C.
Qutluq Khatun
Qutluq Khatun was a Mongol noblewoman of the Ilkhanate period, best known as the mother of the Ilkhanid ruler Ghazan Khan.
-
D.
Qaitmish Khatun
Qaitmish Khatun was a noblewoman of the Ilkhanate period, best known as the mother of the Mongol ruler Arghun.
-
E.
Great Khanum
Great Khanum is an honorific title historically used for a principal or imperial queen consort in Central Asian and Mongol royal courts.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e202075860819088d27d921609a6ce |
completed | April 17, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff7a0ed9c8190a10fa88ee94811cb |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 5:01 a.m.