Triple
T16281110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sanjakbey |
E395264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman administrative office |
C17083
|
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 administrative office Context triple: [sanjakbey, instanceOf, Ottoman administrative office]
-
A.
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.
-
B.
Ottoman educational institution
An Ottoman educational institution is a formal establishment within the Ottoman Empire dedicated to providing religious, legal, and sometimes scientific instruction, typically organized around Islamic scholarship and state administrative needs.
-
C.
Ottoman-era residence
An Ottoman-era residence is a traditional domestic building characterized by inward-focused courtyards, overhanging upper stories, wooden latticework, and a spatial hierarchy separating public and private family areas.
-
D.
Ottoman court title
chosen
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.
-
E.
Turkish public institution
A Turkish public institution is a government-established organization in Türkiye that performs administrative, regulatory, or service-delivery functions in accordance with national laws and public policy.
- 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.