Triple
T15586121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shahzada Parviz Mirza |
E374625
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Parviz |
E748868
|
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: Parviz | Statement: [Shahzada Parviz Mirza, givenName, Parviz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parviz Context triple: [Shahzada Parviz Mirza, givenName, Parviz]
-
A.
Parviz
chosen
Parviz is a masculine given name of Persian origin commonly used in Iran and among Persian-speaking communities.
-
B.
Fariborz
Fariborz is a Persian given name commonly used for men, particularly in Iran and among the Iranian diaspora.
-
C.
Rūzbeh
Rūzbeh was the original Persian name of Ibn al-Muqaffaʿ, the influential 8th-century translator and prose stylist who helped shape early Arabic literature.
-
D.
Abolhassan
Abolhassan is a Persian given name most notably borne by Abolhassan Banisadr, the first President of the Islamic Republic of Iran.
-
E.
Sarrafati
Sarrafati is a surname of likely Middle Eastern or Mediterranean origin, used as a variant form of the name Sarfati.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e4900408190aadb48b001db4169 |
completed | April 16, 2026, 2:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c5166d88190ab14c7779e3e8e1f |
completed | May 9, 2026, 3:01 p.m. |
Created at: April 10, 2026, 4:11 a.m.