Triple
T18625329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatun |
E455268
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Khatun |
—
|
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: Khatun | Statement: [Hatun, relatedTo, Khatun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khatun Context triple: [Hatun, relatedTo, Khatun]
-
A.
Khatun
chosen
Khatun is a historical title used in Turkic and Mongol societies for a noblewoman or queen, often the wife or female counterpart of a khan.
-
B.
Despina Khatun
Despina Khatun was a Byzantine princess who became a consort of the Ilkhanid ruler Abaqa Khan, symbolizing a political alliance between the Byzantine Empire and the Mongol Ilkhanate.
-
C.
Despina Khatun
Despina Khatun was a Byzantine-descended noblewoman who became a prominent consort in the Aq Qoyunlu dynasty through her marriage to ruler Uzun Hasan.
-
D.
Dagi Khatun
Dagi Khatun was a Mongol noblewoman and empress consort of the Yuan dynasty, best known as the mother of Emperor Buyantu Khan.
-
E.
Töregene Khatun
Töregene Khatun was a powerful Mongol empress who served as regent of the Mongol Empire after Ögedei Khan’s death, playing a key role in imperial politics and succession.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f039b408190b51fe770a4c530ec |
completed | April 19, 2026, 9:54 p.m. |
Created at: April 10, 2026, 11:46 a.m.