Triple
T21208527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman military engineering |
E522654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aspect 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: aspect of the Roman army Context triple: [Roman military engineering, instanceOf, aspect of the Roman army]
-
A.
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.
-
B.
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.
-
C.
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.
-
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.
component of the Roman state
A component of the Roman state is any institutional, social, or political element—such as magistracies, assemblies, the Senate, legal frameworks, or provincial administrations—that collectively structured and maintained Roman governance and public life.
- F. None of above. chosen
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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:25 p.m.