Triple
T22899133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayşe Hatun |
E568260
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Seljuk noble |
C37630
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Seljuk noble Context triple: [Ayşe Hatun, instanceOf, Seljuk noble]
-
A.
Timurid noble
A Timurid noble is a high-ranking aristocrat within the Timurid Empire, typically of Turco-Mongol lineage, who held land, military command, and administrative authority under the dynasty founded by Timur (Tamerlane).
-
B.
Seljuk official
chosen
A Seljuk official is an administrative or military functionary serving the Seljuk Empire, responsible for implementing state policies, managing governance, and maintaining order within the sultan’s domains.
-
C.
Zengid ruler
A Zengid ruler is a sovereign or governor from the Zengid dynasty, a 12th–13th century Muslim Turkic ruling house that controlled parts of Syria and northern Iraq, known for its military campaigns against Crusader states and efforts to unify Muslim territories.
-
D.
Seljuk sultan of Rum
A Seljuk sultan of Rum was the Muslim Turkic ruler of the Sultanate of Rum in Anatolia, governing a medieval state that emerged from the Great Seljuk Empire and served as a political and cultural bridge between the Islamic world and Byzantine-influenced Asia Minor.
-
E.
Afghan noble
An Afghan noble is a high-ranking member of Afghanistan’s traditional aristocracy, typically possessing hereditary titles, land, and social influence within tribal or urban elite structures.
- F. None of above.
Provenance (1 batch)
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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:41 p.m.