Triple
T4733768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahadur Shah I |
E105072
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Azam Shah |
E112694
|
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: Azam Shah | Statement: [Bahadur Shah I, sibling, Azam Shah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Azam Shah Context triple: [Bahadur Shah I, sibling, Azam Shah]
-
A.
Azam Shah
chosen
Azam Shah was a Mughal prince and briefly a claimant to the imperial throne in late 17th-century India, known primarily as a son of Emperor Aurangzeb.
-
B.
Ala-ud-Din Alam Shah
Ala-ud-Din Alam Shah was the last ruler of the Sayyid dynasty of the Delhi Sultanate, known for his weak rule and eventual abdication in favor of Bahlul Lodi.
-
C.
Zaman Shah
Zaman Shah was an 18th-century Durrani ruler of Afghanistan, known for his attempts to expand Afghan influence into the Indian subcontinent.
-
D.
Jahan Shah
Jahan Shah was a Mughal prince of India, known primarily as a son of Emperor Bahadur Shah I and a member of the later Mughal imperial lineage.
-
E.
Alauddin Riayat Shah II
Alauddin Riayat Shah II was a 16th-century Malay ruler who became the first sultan of Johor after the fall of the Malacca Sultanate.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6467a1fc819089485b4d76e0edc4 |
completed | March 20, 2026, 3:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be3a0fc0b88190a1eb07f6fb021b86 |
completed | March 21, 2026, 6:26 a.m. |
Created at: March 20, 2026, 1:19 p.m.