Triple
T26441595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian April Uprising |
E665104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Bulgarian history |
C40095
|
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 Bulgarian history Context triple: [Bulgarian April Uprising, instanceOf, event in Bulgarian history]
-
A.
Bulgarian national liberation movement event
chosen
A Bulgarian national liberation movement event is a historical occurrence—such as an uprising, conspiracy, protest, or key political act—undertaken by Bulgarians to resist foreign domination and advance the cause of national independence and self-determination.
-
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 Danish history
A significant occurrence or series of actions situated in Denmark’s past that influenced its political, social, cultural, or economic development.
-
D.
Bulgarian National Revival
The Bulgarian National Revival was a cultural, political, and social movement from the late 18th to the late 19th century that fostered Bulgarian national consciousness, language, education, and the struggle for church and political independence from Ottoman rule.
-
E.
event in British history
A significant occurrence or series of actions within the geographical and political context of Britain that influenced its social, political, economic, or cultural development and is recognized as part of its historical narrative.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:58 p.m.