Triple
T9487000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | testudo formation |
E228786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman military tactic |
C26685
|
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 tactic Context triple: [testudo formation, instanceOf, Roman military tactic]
-
A.
Roman military campaign
A Roman military campaign is a coordinated series of operations conducted by Roman forces, combining strategic planning, logistics, and battlefield tactics to achieve political, territorial, or defensive objectives.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Roman military commander
A Roman military commander is a high-ranking officer responsible for leading legions, planning and executing campaigns, maintaining discipline, and securing Rome’s political and territorial interests through organized warfare.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:55 p.m.