Triple
T33319251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miracle of the Thundering Legion |
E853094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | episode in Roman military history |
C59429
|
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: episode in Roman military history Context triple: [Miracle of the Thundering Legion, instanceOf, episode in Roman military history]
-
A.
episode of the Roman civil wars
An episode of the Roman civil wars is a distinct, temporally bounded conflict event or campaign involving Roman factions whose actions and outcomes contribute to the broader course of the civil wars.
-
B.
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.
-
C.
era of Roman history
An era of Roman history is a distinct chronological period characterized by specific political structures, social dynamics, cultural developments, and major events within the broader timeline of ancient Rome.
-
D.
aspect of the Roman army
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.
-
E.
Roman battle
A Roman battle is a large-scale military engagement in which Roman forces, often organized into legions and auxiliaries, confront enemy armies using disciplined formations, tactical maneuvers, and a combination of infantry, cavalry, and siege weaponry.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:33 a.m.