Triple
T4373833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Serbian Uprising |
E98957
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Serbian history |
C15824
|
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 Serbian history Context triple: [First Serbian Uprising, instanceOf, event in Serbian history]
-
A.
Serbian nationalist movement
The Serbian nationalist movement is a political and cultural current centered on promoting Serbian national identity, sovereignty, and interests, often emphasizing historical narratives of statehood, territorial claims, and ethnic solidarity.
-
B.
Serbian national hero
A Serbian national hero is an individual, real or legendary, celebrated in Serbian history and culture for extraordinary courage, sacrifice, or leadership in defending the nation’s freedom, identity, or values.
-
C.
event in Irish history
An event in Irish history is a significant occurrence or series of actions within Ireland’s past that influenced its political, social, cultural, or economic development.
-
D.
event in the history of Argentina
An event in the history of Argentina is a significant occurrence or development, situated in time and place, that has influenced the nation’s political, social, economic, or cultural trajectory.
-
E.
event in the history of Spain
An event in the history of Spain is a significant occurrence or development within Spanish territory or involving Spanish actors that has contributed to shaping the nation’s political, social, cultural, or economic trajectory over time.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:17 p.m.