Triple
T23695940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iman Pahlavi |
E585444
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object |
Mohammad Reza Pahlavi II
Mohammad Reza Pahlavi II is a member of the former Iranian royal family and the son of exiled Crown Prince Reza Pahlavi.
|
E1640841
|
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: Mohammad Reza Pahlavi II | Statement: [Iman Pahlavi, sibling, Mohammad Reza Pahlavi II]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Mohammad Reza Pahlavi II Triple: [Iman Pahlavi, sibling, Mohammad Reza Pahlavi II]
Generated description
Mohammad Reza Pahlavi II is a member of the former Iranian royal family and the son of exiled Crown Prince Reza Pahlavi.
Provenance (5 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c65ab88190be59a8fb731cf030 |
completed | April 29, 2026, 7:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0ff82846e48190a29e3efbcfad2c92 |
completed | May 22, 2026, 6:31 a.m. |
| NEDg | Description generation | batch_6a0ff93a0dec81909163580a48548e9a |
completed | May 22, 2026, 6:35 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0ff9d952ec81908a5b2640c263e21d |
completed | May 22, 2026, 6:38 a.m. |
Created at: April 17, 2026, 6:52 p.m.