Triple
T21541315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wali of Acre |
E531495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman provincial 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 provincial office Context triple: [Wali of Acre, instanceOf, Ottoman provincial 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 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.
-
C.
Eyalet
An Eyalet is a major administrative division of the Ottoman Empire, governed by a beylerbey and comprising several subordinate districts or sanjaks.
-
D.
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.
-
E.
Ottoman commercial building type
An Ottoman commercial building type is a multifunctional urban structure—such as a bedesten, han, or bazaar—designed to facilitate trade, storage, and sometimes lodging, typically organized around courtyards and integrated into the broader economic and social fabric of the city.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:28 p.m.