Triple
T17941189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vakʿa-i Hayriyye |
E448591
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman history event |
C39290
|
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 history event Context triple: [Vakʿa-i Hayriyye, instanceOf, Ottoman history event]
-
A.
event in the Ottoman Empire
chosen
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.
-
B.
Byzantine history event
A Byzantine history event is a significant occurrence within the Eastern Roman (Byzantine) Empire that influenced its political, religious, military, social, or cultural development.
-
C.
cultural heritage of the Ottoman Empire
The cultural heritage of the Ottoman Empire encompasses the diverse artistic, architectural, literary, religious, and social traditions that developed under Ottoman rule and continue to influence the identities, practices, and built environments of many societies across Europe, the Middle East, and North Africa.
-
D.
event in the Byzantine–Ottoman wars
An "event in the Byzantine–Ottoman wars" is a specific historical occurrence—such as a battle, siege, treaty, or political development—that took place within the broader series of conflicts between the Byzantine Empire and the Ottoman state.
-
E.
Ottoman order
An Ottoman order is a formal honor or decoration bestowed by the Ottoman Empire to recognize distinguished service, loyalty, or achievement in military, civil, or diplomatic fields.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.