Triple
T24812182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manastır |
E620819
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman administrative center |
C17990
|
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 center Context triple: [Manastır, instanceOf, Ottoman administrative center]
-
A.
Ottoman government office
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 religious complex
An Ottoman religious complex is an architectural ensemble centered around a mosque and typically including facilities such as a madrasa, hospice, bath, and charitable institutions, designed to serve the spiritual, educational, and social needs of the community.
-
C.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
-
D.
Turkish principality
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
E.
Eyalet
chosen
An Eyalet is a major administrative division of the Ottoman Empire, governed by a beylerbey and comprising several subordinate districts or sanjaks.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:50 a.m.