Triple
T34687400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahir ibn al-Husayn |
E890789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian-origin military leader |
C33979
|
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-origin military leader Context triple: [Tahir ibn al-Husayn, instanceOf, Persian-origin military leader]
-
A.
Persian military commander
chosen
A Persian military commander is a high-ranking leader responsible for planning, directing, and overseeing the armed forces of Persia in warfare and defense operations.
-
B.
Turkic military leader
A Turkic military leader is a commander of Turkic origin who organizes, directs, and leads armed forces in warfare, defense, or expansion, often shaping the political and cultural trajectory of Turkic societies.
-
C.
Achaemenid noble
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.
-
D.
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.
-
E.
Iranian noble
An Iranian noble is a high-ranking member of Iran’s traditional aristocracy, historically distinguished by lineage, landownership, political influence, and social prestige within Persian and later Iranian society.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.