Triple
T5279885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John de Beauchamp, 1st Baron Beauchamp de Warwick |
E119468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval military commander |
C11520
|
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 commander Context triple: [John de Beauchamp, 1st Baron Beauchamp de Warwick, instanceOf, medieval military commander]
-
A.
medieval military leader
chosen
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.
-
B.
late medieval ruler
A late medieval ruler is a sovereign who governed a kingdom or principality in Europe roughly between the 13th and 15th centuries, navigating feudal structures, emerging centralized authority, and complex dynastic, religious, and military conflicts.
-
C.
Scottish knight
A Scottish knight is a medieval mounted warrior of Scottish origin, bound by chivalric codes and feudal allegiance, distinguished by regional arms, armor, and participation in Scotland’s historic conflicts.
-
D.
condottiero
A condottiero is a professional military leader or mercenary captain, particularly in Renaissance Italy, who commanded troops under contract for city-states, princes, or the papacy.
-
E.
medieval Christian warriors
Medieval Christian warriors were armed combatants, such as knights and crusaders, who fought under the banner of Christian faith and feudal allegiance in religiously and politically motivated conflicts.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:52 p.m.