Triple
T19229894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christianisation of Pomerania |
E480841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval history event |
C13724
|
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: medieval history event Context triple: [Christianisation of Pomerania, instanceOf, medieval history event]
-
A.
medieval event
chosen
A medieval event is a historically themed gathering or occurrence set in or inspired by the Middle Ages, often featuring period-appropriate customs, attire, activities, and social structures.
-
B.
medieval civilization
A medieval civilization is a complex society that flourished roughly between the 5th and 15th centuries, characterized by feudal social structures, agrarian economies, religious dominance (often by the Church), fortified settlements, and evolving political institutions that laid foundations for the modern state.
-
C.
medieval people
Medieval people are individuals living during the Middle Ages, typically characterized by feudal social structures, agrarian lifestyles, religious centrality, and limited technological development compared to later periods.
-
D.
medievalist
A medievalist is a scholar or enthusiast who studies and interprets the history, culture, literature, and societies of the Middle Ages.
-
E.
war in the Middle Ages
War in the Middle Ages encompasses the organized, often feudal-based conflicts fought between kingdoms, nobles, and religious powers using evolving military technologies, tactics, and social structures from roughly the 5th to the 15th century.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:25 p.m.