Triple
T4297988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirak Mirza Ghiyas |
E99762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal-era architect |
C13577
|
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-era architect Context triple: [Mirak Mirza Ghiyas, instanceOf, Mughal-era architect]
-
A.
subah of the Mughal Empire
A subah of the Mughal Empire was a major provincial administrative division governed by a subahdar, responsible for local governance, revenue collection, and military control within its territory.
-
B.
Ottoman architect
An Ottoman architect is a designer and builder responsible for planning, engineering, and aesthetically shaping structures within the cultural, religious, and political context of the Ottoman Empire.
-
C.
Mughal official
chosen
A Mughal official was an appointed administrator or noble in the Mughal Empire responsible for governing territories, collecting revenue, maintaining law and order, and implementing imperial policies on behalf of the emperor.
-
D.
Italian Renaissance architect
An Italian Renaissance architect is a designer of buildings who, during the 14th–16th centuries in Italy, revived and reinterpreted classical Roman forms using symmetry, proportion, and geometric harmony to create innovative civic, religious, and domestic structures.
-
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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:08 p.m.