Triple
T7133976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir Sohrab Khan Talpur |
E166258
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Sohrab |
E124244
|
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: Sohrab | Statement: [Mir Sohrab Khan Talpur, givenName, Sohrab]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sohrab Context triple: [Mir Sohrab Khan Talpur, givenName, Sohrab]
-
A.
Sohrab
chosen
Sohrab is a tragic hero in the Persian epic Shahnameh, famed as the valiant but ill-fated son of the champion Rostam.
-
B.
Shobab
Shobab is a lesser-known son of King David of Israel and Bathsheba, mentioned briefly in the Hebrew Bible.
-
C.
Reza
Reza is the given name of Reza Shah Pahlavi, the founder of the Pahlavi dynasty and modernizing monarch of Iran in the early 20th century.
-
D.
Malek
Malek is a given name and surname of Arabic origin commonly used across the Middle East and other Muslim-majority regions.
-
E.
Jamshid
Jamshid is a legendary king in Persian mythology, renowned for his long, prosperous reign and his central role in ancient Iranian cultural and epic traditions.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e68f15bc8190a4d82b8ee388f497 |
completed | March 27, 2026, 8:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7a344fb4881908f6b6e33706e0192 |
completed | March 28, 2026, 9:45 a.m. |
Created at: March 27, 2026, 2:45 p.m.