Triple
T4231188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dilras Banu Begum |
E94583
|
entity |
| Predicate | spouseReignTitle |
P17687
|
FINISHED |
| Object | Emperor of the Mughal Empire |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Emperor of the Mughal Empire | Statement: [Dilras Banu Begum, spouseReignTitle, Emperor of the Mughal Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseReignTitle Context triple: [Dilras Banu Begum, spouseReignTitle, Emperor of the Mughal Empire]
-
A.
hasSpouseTitle
chosen
Indicates that a person’s spouse holds a particular title or honorific designation.
-
B.
consortTitleAtCoronation
Indicates the formal title held by a royal consort specifically at the time of a coronation.
-
C.
monarchSpouseReignStart
Indicates the date when a monarch’s spouse began their role as consort during the monarch’s reign.
-
D.
spouseIsLastIndependentRulerOf
Indicates that the subject’s spouse is recognized as the final ruler of a polity who governed independently, before loss of sovereignty or incorporation into another authority.
-
E.
currentTitleHolderSpouseOf
Indicates that one entity is the current spouse of the individual who presently holds a specified title.
- F. None of above.
Provenance (3 batches)
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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e62e3c881909ffb9269ba9018b9 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.