Triple
T23413427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine expeditionary force in Italy |
E560140
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine army formation |
C19405
|
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: Byzantine army formation Context triple: [Byzantine expeditionary force in Italy, instanceOf, Byzantine army formation]
-
A.
army formation
chosen
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
-
B.
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.
-
C.
hoplite army
A hoplite army is a heavily armed infantry force of citizen-soldiers fighting in close formation, typically organized into phalanxes using spears, shields, and armor for collective defense and offense.
-
D.
militia-style military formation
A militia-style military formation is an organized group of primarily non-professional, part-time fighters drawn from the civilian population, structured for local defense or irregular warfare under limited formal military hierarchy and training.
-
E.
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.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:39 p.m.