Triple
T14205909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castilian campaign of 1367 |
E352094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval military expedition |
C17994
|
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 expedition Context triple: [Castilian campaign of 1367, instanceOf, medieval military expedition]
-
A.
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.
-
B.
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.
-
C.
Crusades battle
A Crusades battle is a large-scale medieval military engagement between Christian and Muslim forces (and their allies) fought primarily in the Eastern Mediterranean and surrounding regions as part of the religiously motivated campaigns known as the Crusades.
-
D.
Reconquista campaign
chosen
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.
-
E.
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.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:05 a.m.