Triple
T3176941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumtaz Mahal |
E66486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal empress |
C12382
|
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: Mughal empress Context triple: [Mumtaz Mahal, instanceOf, Mughal empress]
-
A.
Byzantine empress
A Byzantine empress is the imperial consort or reigning female sovereign of the Byzantine Empire, wielding varying degrees of political, ceremonial, and cultural influence within the court and empire.
-
B.
Empress of Russia
The Empress of Russia is the female sovereign ruler or consort at the apex of the Russian imperial hierarchy, embodying supreme political authority, dynastic continuity, and ceremonial leadership within the Russian Empire.
-
C.
Empress of Japan
The Empress of Japan is the female consort or reigning sovereign of the Japanese imperial family, embodying ceremonial, cultural, and symbolic roles within the world’s oldest continuous hereditary monarchy.
-
D.
former Empress of Japan
A former Empress of Japan is a woman who previously held the title of Empress as the wife or consort of a reigning Japanese Emperor and has since left the position due to the Emperor’s abdication or death.
-
E.
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.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:06 p.m.