Triple
T27857314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman auxiliary units |
E704123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Roman army |
C44363
|
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: component of the Roman army Context triple: [Roman auxiliary units, instanceOf, component of the Roman army]
-
A.
aspect of the Roman army
chosen
An aspect of the Roman army is a distinct component, practice, structure, or role within Rome’s military system that contributed to its organization, effectiveness, and operations.
-
B.
component of Roman military logistics
A component of Roman military logistics is any organizational unit, infrastructure element, or procedural system that supports the provisioning, transport, storage, and distribution of supplies necessary to sustain Roman forces during campaigns and garrison duties.
-
C.
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.
-
D.
Roman legion
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.
-
E.
Roman military tactic
A Roman military tactic is a structured battlefield maneuver or strategic approach employed by Roman forces to maximize discipline, cohesion, and tactical advantage over their enemies.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 6:15 p.m.