Triple
T4289737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhammad Akbar |
E97358
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Shahzada |
E379611
|
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: Shahzada | Statement: [Muhammad Akbar, title, Shahzada]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shahzada Context triple: [Muhammad Akbar, title, Shahzada]
-
A.
Shahzada
chosen
Shahzada is a royal title used in Persianate and South Asian cultures to denote a prince or son of a monarch.
-
B.
Mirza
Mirza is a historical noble title of Persian and Central Asian origin, commonly borne by princes and high-ranking members of royal and aristocratic families.
-
C.
Cassim
Cassim is Ali Baba’s wealthy but greedy older brother in the classic Middle Eastern folk tale "Ali Baba and the Forty Thieves."
-
D.
Sultan
The Sultan was the supreme monarch of the Ottoman Empire, wielding ultimate political, military, and religious authority over its vast territories.
-
E.
Shah
Shah is a royal title historically used for monarchs and rulers in Persia (Iran) and other regions of the Islamic world.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35061f5448190b3356b29a9129160 |
completed | March 12, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5c7307e3481909dfb55018f359589 |
completed | March 14, 2026, 8:38 p.m. |
Created at: March 12, 2026, 11:08 p.m.