Triple
T17940845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasan Predojević |
E448581
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bosnian Ottoman official |
C32288
|
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: Bosnian Ottoman official Context triple: [Hasan Predojević, instanceOf, Bosnian Ottoman official]
-
A.
Ottoman Albanian noble
An Ottoman Albanian noble was a member of the Albanian-origin elite within the Ottoman Empire who held hereditary or state-granted titles, land, and administrative or military authority, often serving as intermediaries between the central government and local populations.
-
B.
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.
-
C.
Ottoman politician
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 person
chosen
An Ottoman person is an individual who lived under or identified with the multiethnic, multireligious Ottoman Empire, shaped by its social, cultural, and political institutions.
-
E.
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.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.