Triple
T5907549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Müveddet Kadın |
E131377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Ottoman imperial harem |
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: member of the Ottoman imperial harem Context triple: [Müveddet Kadın, instanceOf, member of the Ottoman imperial harem]
-
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.
member of the Ottoman dynasty
A member of the Ottoman dynasty is an individual belonging by birth or marriage to the ruling imperial family of the Ottoman Empire, historically entitled to varying degrees of political influence, privilege, and succession rights.
-
D.
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.
-
E.
Mughal noblewoman
A Mughal noblewoman is an elite female member of the Mughal courtly aristocracy, distinguished by her lineage, wealth, political influence, and participation in the cultural and social life of the empire.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:59 p.m.