Triple
T18166116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgrade Pashaluk |
E434898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman administrative unit |
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 unit Context triple: [Belgrade Pashaluk, instanceOf, Ottoman administrative unit]
-
A.
Eyalet
chosen
An Eyalet is a major administrative division of the Ottoman Empire, governed by a beylerbey and comprising several subordinate districts or sanjaks.
-
B.
part of the Ottoman Empire
A "part of the Ottoman Empire" is a territorial, administrative, or political subdivision that was under the sovereignty and governance of the Ottoman state during its existence.
-
C.
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.
-
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.
province of the Byzantine Empire
A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:30 a.m.