Triple
T16281251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nişancı |
E395267
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-ranking Ottoman official |
C9522
|
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: high-ranking Ottoman official Context triple: [nişancı, instanceOf, high-ranking Ottoman 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.
Timurid official
A Timurid official was an administrative or military functionary serving the Timurid Empire, responsible for implementing imperial policies, managing provincial governance, and maintaining order and revenue collection under the authority of the Timurid rulers.
-
C.
Ottoman politician
chosen
An Ottoman politician was a statesman or public official within the Ottoman Empire responsible for participating in governance, administration, and policy-making at imperial or provincial levels.
-
D.
Ottoman general
An Ottoman general is a high-ranking military commander in the Ottoman Empire responsible for planning, leading, and overseeing major military campaigns and the administration of troops.
-
E.
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.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:05 a.m.