Triple
T17882936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anatolian kazasker |
E447133
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman military judicial office |
C37216
|
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 military judicial office Context triple: [Anatolian kazasker, instanceOf, Ottoman military judicial office]
-
A.
Ottoman government office
chosen
An Ottoman government office is an administrative institution within the Ottoman Empire responsible for managing specific state functions such as taxation, justice, military affairs, or provincial governance under the authority of the sultan and central bureaucracy.
-
B.
Ottoman court title
An Ottoman court title is an official designation granted within the Ottoman imperial hierarchy that denotes a person's rank, role, and privileges in the administration, judiciary, or royal household.
-
C.
component of Ottoman army
A component of the Ottoman army is a distinct organizational, functional, or tactical unit—such as infantry, cavalry, artillery, or auxiliary corps—that collectively contributed to the empire’s military structure and operations.
-
D.
Ottoman law
Ottoman law refers to the complex legal system of the Ottoman Empire, combining Islamic (Sharia) principles, sultanic decrees (Kanun), and customary practices to govern its diverse populations and administrative affairs.
-
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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:18 a.m.