Triple

T36617166
Position Surface form Disambiguated ID Type / Status
Subject Vizier of the Seljuk Empire E903633 entity
Predicate notableOfficeHolder P5750 FINISHED
Object Mu'ayyid al-Mulk
Mu'ayyid al-Mulk was a prominent Persian statesman and administrator who served as a powerful vizier during the Seljuk Empire’s height.
E2196254 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: Mu'ayyid al-Mulk | Statement: [Vizier of the Seljuk Empire, notableOfficeHolder, Mu'ayyid al-Mulk]
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: Mu'ayyid al-Mulk
Triple: [Vizier of the Seljuk Empire, notableOfficeHolder, Mu'ayyid al-Mulk]
Generated description
Mu'ayyid al-Mulk was a prominent Persian statesman and administrator who served as a powerful vizier during the Seljuk Empire’s height.

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_69f76e6960e4819092047756ceb9a17e completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c4821cd8819082f0c280b8862f4b completed May 3, 2026, 9:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3a3810a1bc819081415efd454e2c15 completed June 23, 2026, 7:38 a.m.
NEDg Description generation batch_6a3a3bba39448190a21dc14da0144d49 completed June 23, 2026, 7:54 a.m.
NED2 Entity disambiguation (via description) batch_6a3a3d878b108190bf736f6f39b32874 completed June 23, 2026, 8:02 a.m.
Created at: May 3, 2026, 4:11 p.m.