Triple
T30872258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaysersberg, Erzurum Vilayet, Ottoman Empire |
E786373
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | populated place in the Ottoman Empire |
C57249
|
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: populated place in the Ottoman Empire Context triple: [Kaysersberg, Erzurum Vilayet, Ottoman Empire, instanceOf, populated place in the Ottoman Empire]
-
A.
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.
-
B.
event in the Ottoman Empire
An event in the Ottoman Empire is any significant occurrence—political, military, social, economic, or cultural—that took place within or directly affected the Ottoman state and its territories during its existence.
-
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.
populated place in Bosnia and Herzegovina
A populated place in Bosnia and Herzegovina is a geographically defined settlement, such as a city, town, or village, where people reside within the country's borders.
-
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. chosen
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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:48 p.m.