Triple
T3092015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haman |
E64502
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian royal official |
C5196
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Persian royal official Context triple: [Haman, instanceOf, Persian royal official]
-
A.
Abbasid official
An Abbasid official was a bureaucrat or administrator serving the Abbasid Caliphate, responsible for managing state affairs such as taxation, justice, military logistics, and provincial governance within the empire’s centralized administrative system.
-
B.
Byzantine official
A Byzantine official is a government functionary of the Eastern Roman (Byzantine) Empire responsible for administering imperial policies, finances, justice, or military affairs within its complex bureaucratic hierarchy.
-
C.
Achaemenid ruler
An Achaemenid ruler is a monarch of the ancient Persian Achaemenid Empire who exercised centralized authority over a vast, multicultural territory through a system of satrapies, royal roads, and imperial administration.
-
D.
grand vizier
A grand vizier is the highest-ranking minister or chief advisor to a sovereign, wielding extensive administrative and political authority on the ruler’s behalf.
-
E.
royal courtier
chosen
A royal courtier is a member of a monarch’s household who attends the ruler, manages or influences court affairs, and advances political, social, or personal interests within the royal court.
- F. None of above.
Provenance (1 batch)
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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:03 p.m.