Triple
T31529992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reorganization of Frankish cavalry |
E804450
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankish military reform |
C41367
|
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: Frankish military reform Context triple: [Reorganization of Frankish cavalry, instanceOf, Frankish military reform]
-
A.
Bavarian military reform
Bavarian military reform refers to the series of structural, organizational, and doctrinal changes implemented in Bavaria’s armed forces—particularly in the 19th and early 20th centuries—to modernize its military capabilities, align with broader German military standards, and enhance effectiveness in both national defense and coalition warfare.
-
B.
Frankish military contingent
A Frankish military contingent is a temporary, organized group of Frankish warriors and support personnel assembled under a designated leader to conduct specific military operations or campaigns.
-
C.
Carolingian frontier march
A Carolingian frontier march was a militarized border territory of the Carolingian Empire, governed by a margrave and designed to defend and expand imperial frontiers.
-
D.
Frankish army
chosen
The Frankish army was the military force of the Frankish kingdoms, characterized by a mix of heavy cavalry, infantry levies, and feudal contingents that played a central role in shaping early medieval Western Europe.
-
E.
Carolingian march
A Carolingian march was a frontier border territory of the Carolingian Empire, governed by a margrave and organized for military defense and administration against external threats.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10 p.m.