Triple
T30733663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | army of Gaius Cassius Longinus |
E782486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman Republican army |
C23903
|
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: Roman Republican army Context triple: [army of Gaius Cassius Longinus, instanceOf, Roman Republican army]
-
A.
Roman legion
chosen
A Roman legion is a large, highly organized military unit of the ancient Roman army, typically composed of several thousand heavily armed infantry supported by cavalry and specialized troops.
-
B.
Roman territorial unit
A Roman territorial unit is an administrative division of land within the Roman state, defined for purposes such as governance, taxation, military organization, and legal jurisdiction.
-
C.
Roman auxiliary units
Roman auxiliary units were non-citizen military formations that supported the legions by providing specialized troops—such as infantry, cavalry, and archers—from diverse provincial populations across the empire.
-
D.
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.
-
E.
Roman soldier
A Roman soldier is a disciplined, heavily trained infantryman of ancient Rome’s military, equipped with standardized armor and weapons, who served to expand and protect the Roman state.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:37 p.m.