Triple
T15004341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Salim |
E377670
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Shah Begum |
E348424
|
NE 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: Shah Begum | Statement: [Prince Salim, spouse, Shah Begum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shah Begum Context triple: [Prince Salim, spouse, Shah Begum]
-
A.
Shah Begum
chosen
Shah Begum was a Timurid-era noblewoman known as the daughter of Qutlugh Nigar Khanum and a member of the Mughal imperial family.
-
B.
Maham Begum
Maham Begum was a chief consort of the Mughal emperor Babur and the mother of his successor, Humayun.
-
C.
Badshah Begum
Badshah Begum was a prominent Mughal empress and influential royal consort in 18th-century India.
-
D.
Kandahari Begum
Kandahari Begum was a Mughal princess and the first wife of Emperor Shah Jahan, known for her Timurid lineage and political significance in the Mughal court.
-
E.
Sultanam Begum
Sultanam Begum was a Mughal noblewoman known primarily as the mother of Ruqaiya Sultan Begum, chief consort of the emperor Akbar.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7312ae48190bdaf91ecced6657e |
completed | April 15, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff133571008190b7e7867208095b90 |
completed | May 9, 2026, 10:57 a.m. |
Created at: April 10, 2026, 2:54 a.m.