Triple
T16760217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsknechte |
E407321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early modern military unit type |
C29180
|
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: early modern military unit type Context triple: [Landsknechte, instanceOf, early modern military unit type]
-
A.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
Renaissance military tradition
chosen
Renaissance military tradition encompasses the evolving practices, technologies, doctrines, and social institutions of warfare in Europe between the 14th and 17th centuries, marked by the transition from feudal levies to professional armies, the rise of gunpowder weapons, and the integration of humanist thought into military theory.
-
C.
Parliamentarian cavalry
Parliamentarian cavalry were mounted troops loyal to the English Parliament during the Civil War, combining mobility, shock tactics, and disciplined formations to challenge Royalist forces on the battlefield.
-
D.
Spanish imperial military unit
A Spanish imperial military unit is an organized armed formation under the authority of the Spanish Empire, structured for conquest, defense, and control of its territories across Europe and overseas.
-
E.
armored cavalry formation
An armored cavalry formation is a highly mobile, heavily armored military unit organized to conduct reconnaissance, security, and shock action on the battlefield using tanks and other armored fighting vehicles.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.