Triple
T35762423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Mansur Nasir al-Din Muhammad |
E1033912
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Syrian ruler |
C47176
|
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: medieval Syrian ruler Context triple: [Al-Mansur Nasir al-Din Muhammad, instanceOf, medieval Syrian ruler]
-
A.
Artuqid ruler
An Artuqid ruler is a sovereign or governor from the Artuqid dynasty, a Turkoman ruling family that controlled various principalities in Upper Mesopotamia and Anatolia between the late 11th and early 15th centuries.
-
B.
Alaouite ruler
An Alaouite ruler is a sovereign from the Alaouite dynasty of Morocco, which has governed the country since the 17th century, combining religious legitimacy as sharifs (descendants of the Prophet Muhammad) with political authority over the Moroccan state.
-
C.
Mamluk ruler
chosen
A Mamluk ruler is a sovereign who rose from a military slave background within the Mamluk system to wield political and military authority, often governing Islamic states such as medieval Egypt and Syria.
-
D.
Arab ruler
An Arab ruler is a sovereign leader from an Arab nation or territory who exercises political authority, governance, and representation over their people, often within a monarchical, emirate, or other traditional leadership system.
-
E.
Ayyubid prince
An Ayyubid prince is a male member of the ruling family of the medieval Ayyubid dynasty, typically holding territorial authority, military command, or administrative responsibilities within the dynasty’s fragmented domains in the Middle East.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.