Triple
T37390717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoraya |
E928696
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nasrid-era noblewoman |
C35770
|
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: Nasrid-era noblewoman Context triple: [Zoraya, instanceOf, Nasrid-era noblewoman]
-
A.
medieval Spanish noblewoman
chosen
A medieval Spanish noblewoman is an aristocratic woman in the Iberian Middle Ages who holds social prestige, land-based wealth, and influence through lineage, marriage alliances, and patronage within a feudal and often courtly setting.
-
B.
Fatimid noblewoman
A Fatimid noblewoman is an elite female member of the Fatimid Caliphate’s ruling or aristocratic families, distinguished by her political influence, wealth, education, and participation in courtly, religious, and cultural life.
-
C.
Arab noblewoman
An Arab noblewoman is a high-status woman of Arab heritage, often belonging to a historically influential family or lineage, who embodies cultural refinement, social responsibility, and traditional or contemporary forms of leadership within her community.
-
D.
Safavid noblewoman
A Safavid noblewoman is an elite female member of Safavid Iran’s ruling or aristocratic families, whose status, wealth, and influence were shaped by court politics, kinship ties, and the cultural and religious norms of the Safavid dynasty.
-
E.
Timurid princess
A Timurid princess is a noblewoman of the Timurid dynasty, typically involved in dynastic politics, cultural patronage, and the consolidation of power across Central and South Asia between the 14th and 16th centuries.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.