Triple
T15703725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badauni |
E380655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mughal historian |
C13976
|
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 historian Context triple: [Badauni, instanceOf, Mughal historian]
-
A.
Mughal official
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.
-
B.
Indian historian
chosen
An Indian historian is a scholar who researches, analyzes, and interprets the history of the Indian subcontinent, using primary and secondary sources to construct narratives and explanations of its past.
-
C.
Mughal court chronicle
A Mughal court chronicle is an official historical narrative, often commissioned by the emperor, that records the political events, administrative affairs, cultural life, and imperial ideology of the Mughal court.
-
D.
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.
-
E.
member of the Mughal dynasty
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.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:45 a.m.