Triple
T7098586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Crusades |
E165393
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval military campaign |
C17502
|
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 military campaign Context triple: [Northern Crusades, instanceOf, medieval military campaign]
-
A.
war in the Middle Ages
chosen
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.
-
B.
papal military campaign
A papal military campaign is an organized armed expedition initiated, sanctioned, or led by the pope or the Papal States to pursue religious, political, or territorial objectives.
-
C.
Roman military campaign
A Roman military campaign is a coordinated series of operations conducted by Roman forces, combining strategic planning, logistics, and battlefield tactics to achieve political, territorial, or defensive objectives.
-
D.
medieval military leader
A medieval military leader is a high-ranking commander responsible for organizing, directing, and inspiring armed forces in warfare during the Middle Ages, often balancing battlefield tactics with feudal, political, and religious obligations.
-
E.
Reconquista campaign
A Reconquista campaign is a coordinated military and political effort by Christian kingdoms in medieval Iberia to reclaim territories under Muslim rule, typically involving prolonged warfare, shifting alliances, and religiously framed objectives.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:42 p.m.