Triple
T10233469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamil-ud-Din Begum |
E243401
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal royal consort |
C12681
|
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 royal consort Context triple: [Jamil-ud-Din Begum, instanceOf, Mughal royal consort]
-
A.
Mughal empress consort
chosen
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.
-
B.
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.
-
C.
Mughal empress
A Mughal empress is the principal wife or consort of a Mughal emperor, wielding varying degrees of political, cultural, and domestic influence within the imperial court of the Mughal Empire.
-
D.
Mughal princess
A Mughal princess is a royal woman of the Mughal Empire, typically involved in courtly politics, patronage of arts and architecture, and the preservation and exercise of dynastic power and cultural influence.
-
E.
Vijayanagara royal consort
A Vijayanagara royal consort is a queen or principal spouse of a Vijayanagara emperor, holding ceremonial, political, and dynastic significance within the imperial court of the Vijayanagara 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:20 a.m.