Triple
T14787256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Raunaq Zamani |
E347559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Mughal royal family |
C33485
|
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 Mughal royal family Context triple: [Princess Raunaq Zamani, instanceOf, member of Mughal royal family]
-
A.
member of the Mughal dynasty
chosen
A member of the Mughal dynasty is an individual belonging by birth or marriage to the imperial Timurid-origin ruling family that governed large parts of the Indian subcontinent from the early 16th to the mid-19th century.
-
B.
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.
-
C.
member of a royal family
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
-
D.
Salian dynasty member
A Salian dynasty member is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from 1024 to 1125, originating from the Frankish nobility along the Rhine.
-
E.
member of the Khalji dynasty
A member of the Khalji dynasty is an individual belonging to the Turkic-origin ruling family that controlled the Delhi Sultanate in northern India during the late 13th and early 14th 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.