Triple
T30030162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forces of Licinius I |
E762992
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman military force |
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 military force Context triple: [Forces of Licinius I, instanceOf, Roman military force]
-
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 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.
-
C.
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.
-
D.
Roman military equipment
Roman military equipment encompasses the standardized weapons, armor, tools, and gear used by Roman soldiers to ensure effectiveness, discipline, and adaptability in warfare across the empire.
-
E.
ancient Roman paramilitary corps
An ancient Roman paramilitary corps is a semi-military organization operating alongside or outside the formal legions, tasked with security, policing, or specialized combat roles in support of Roman state authority.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:49 p.m.