Triple
T29708640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istanbul Government |
E751713
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman imperial administration |
C50926
|
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: Ottoman imperial administration Context triple: [Istanbul Government, instanceOf, Ottoman imperial administration]
-
A.
Ottoman order
An Ottoman order is a formal honor or decoration bestowed by the Ottoman Empire to recognize distinguished service, loyalty, or achievement in military, civil, or diplomatic fields.
-
B.
Ottoman court institution
chosen
An Ottoman court institution is a formal body within the Ottoman legal system responsible for administering justice, recording legal transactions, and resolving disputes according to Islamic law and imperial regulations.
-
C.
Mughal administration
Mughal administration was a centralized imperial governance system in South Asia that combined Persian bureaucratic practices, a hierarchical mansabdari (rank) system, and regional autonomy to manage revenue, military, and justice across a diverse empire.
-
D.
Ottoman historiography
Ottoman historiography is the study and interpretation of the history of the Ottoman Empire, encompassing its political, social, economic, and cultural developments as constructed and analyzed by contemporary and later historians.
-
E.
Ottoman provincial governors
Ottoman provincial governors were imperial officials appointed by the sultan to administer provinces, collect taxes, maintain order, and implement central policies while balancing local power structures within the Ottoman Empire.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:29 p.m.