Triple
T10791451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitlis Vilayet |
E254588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of the Ottoman Empire |
C10122
|
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: administrative division of the Ottoman Empire Context triple: [Bitlis Vilayet, instanceOf, administrative division of the Ottoman Empire]
-
A.
Eyalet
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
chosen
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.
administrative district of the Holy Roman Empire
An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
-
D.
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.
-
E.
former subdivision of the Russian Empire
A former subdivision of the Russian Empire is an obsolete administrative-territorial unit that once functioned as part of the empire’s governmental structure but no longer exists in its original form.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:17 p.m.