Triple
T16695718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ismail II |
E405709
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Taklu Khanum |
E438705
|
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: Taklu Khanum | Statement: [Ismail II, spouse, Taklu Khanum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taklu Khanum Context triple: [Ismail II, spouse, Taklu Khanum]
-
A.
Dilaram Khanum
Dilaram Khanum was a Safavid royal consort and the mother of Shah Safi I of Persia in the 17th century.
-
B.
Tajlu Khanum
chosen
Tajlu Khanum was a prominent Safavid royal consort and queen mother, best known as the influential mother of Shah Tahmasp I of Iran.
-
C.
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.
-
D.
Great Khanum
Great Khanum is an honorific title historically used for a principal or imperial queen consort in Central Asian and Mongol royal courts.
-
E.
Anna Khanum
Anna Khanum was a royal consort known primarily as the wife of Safi I, a 17th-century Safavid Shah of Persia.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eadc35881909fb0cc405a0e2fae |
completed | April 18, 2026, 12:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00919d02088190acecb1a62a100255 |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:19 a.m.