Triple
T38422117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fakhr al-Din ibn al-Shaykh |
E903254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ayyubid military commander |
C63170
|
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: Ayyubid military commander Context triple: [Fakhr al-Din ibn al-Shaykh, instanceOf, Ayyubid military commander]
-
A.
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.
-
B.
Mamluk ruler
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.
-
C.
Canaanite military commander
A Canaanite military commander is a high-ranking leader responsible for organizing, directing, and overseeing Canaanite armed forces in warfare, defense, and territorial control.
-
D.
Ottoman general
An Ottoman general is a high-ranking military commander in the Ottoman Empire responsible for planning, leading, and overseeing major military campaigns and the administration of troops.
-
E.
Persian military commander
A Persian military commander is a high-ranking leader responsible for planning, directing, and overseeing the armed forces of Persia in warfare and defense operations.
- F. None of above. chosen
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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.