Triple
T5247698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayşe Hafsa Sultan |
E118505
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman royal consort |
C17255
|
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: Ottoman royal consort Context triple: [Ayşe Hafsa Sultan, instanceOf, Ottoman royal consort]
-
A.
Ottoman consort
chosen
An Ottoman consort was a woman in the Ottoman imperial harem who, as a wife or favored companion of the sultan, held varying degrees of social, political, and ceremonial influence within the court.
-
B.
Ottoman princess
An Ottoman princess is a female member of the Ottoman dynasty, typically the daughter, sister, or close female relative of a sultan, who held significant social status, political influence, and cultural patronage within the imperial court.
-
C.
Mughal empress consort
A Mughal empress consort is the principal wife of a reigning Mughal emperor, holding significant ceremonial status, political influence, and often patronage roles within the imperial court.
-
D.
Byzantine empress consort
A Byzantine empress consort was the wife of a reigning Byzantine emperor who held significant ceremonial, political, and sometimes religious influence at the imperial court, though her authority was formally derived from her marriage rather than direct rule.
-
E.
royal consort
A royal consort is the spouse of a reigning monarch who holds a recognized position at court, often with ceremonial duties but typically without sovereign authority.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:50 p.m.