Triple
T10433894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hystaspes |
E245986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian nobleman |
C13304
|
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 nobleman Context triple: [Hystaspes, instanceOf, Persian nobleman]
-
A.
Achaemenid noble
chosen
An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
-
B.
Sasanian king
A Sasanian king is the sovereign ruler of the Sasanian Empire, wielding supreme political, military, and religious authority over its territories and subjects.
-
C.
Ethiopian nobleman
An Ethiopian nobleman is a high-ranking member of Ethiopia’s traditional aristocracy, historically holding land, political authority, and social prestige within the Ethiopian imperial or regional hierarchy.
-
D.
Armenian prince
An Armenian prince is a nobleman of Armenia’s historical aristocracy, often ruling a principality or region and serving as a military and political leader within the Armenian kingdom or under foreign suzerainty.
-
E.
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.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:14 p.m.