Triple
T22608983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Henry Bagenal |
E566640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Elizabethan soldier |
C42646
|
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: Elizabethan soldier Context triple: [Sir Henry Bagenal, instanceOf, Elizabethan soldier]
-
A.
13th-century English soldier
A 13th-century English soldier is a professional or levied fighting man serving the English crown or a feudal lord, typically equipped with mail armor, shield, and sword or spear, and engaged in campaigns, castle garrisons, and local conflicts shaped by medieval feudal warfare.
-
B.
English Civil War officer
An English Civil War officer is a commissioned military leader who commanded troops for either the Royalist or Parliamentarian forces during the mid-17th-century conflict in England.
-
C.
Tudor-period nobleman
A Tudor-period nobleman is a high-ranking member of the English aristocracy between 1485 and 1603, wielding political influence, land-based wealth, and social authority under the Tudor monarchy.
-
D.
16th-century military leader
chosen
A 16th-century military leader is a high-ranking commander who directed armies and campaigns during the 1500s, navigating the era’s evolving gunpowder warfare, dynastic conflicts, and emerging nation-states.
-
E.
Tudor-era noble
A Tudor-era noble is a high-ranking member of England’s aristocracy during the Tudor dynasty (1485–1603), wielding political influence, land-based wealth, and social prestige within a rigid hierarchical court and feudal system.
- 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 2:56 p.m.