Triple
T21837875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Fire of 1879 in Sarajevo |
E539167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Sarajevo |
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: event in Sarajevo Context triple: [Great Fire of 1879 in Sarajevo, instanceOf, event in Sarajevo]
-
A.
event in the Bosnian War
An event in the Bosnian War is a specific, temporally and geographically bounded occurrence—such as a battle, massacre, political decision, or diplomatic action—that significantly influenced the course, dynamics, or consequences of the conflict in Bosnia and Herzegovina between 1992 and 1995.
-
B.
event in Serbian history
A significant occurrence or development within the historical timeline of Serbia that influenced its political, social, cultural, or territorial evolution.
-
C.
event in the Kosovo War
A specific incident, operation, or development that occurred during the Kosovo War, involving military, political, or humanitarian actions and their immediate consequences.
-
D.
battle of the Croatian War of Independence
A battle of the Croatian War of Independence is an armed engagement between Croatian and opposing forces, occurring between 1991 and 1995 within the broader conflict for Croatia’s independence, characterized by specific locations, participants, objectives, and outcomes.
-
E.
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.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:55 p.m.