Triple
T33319250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miracle of the Thundering Legion |
E853094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military miracle tradition |
C61611
|
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: military miracle tradition Context triple: [Miracle of the Thundering Legion, instanceOf, military miracle tradition]
-
A.
Renaissance military tradition
Renaissance military tradition encompasses the evolving practices, technologies, doctrines, and social institutions of warfare in Europe between the 14th and 17th centuries, marked by the transition from feudal levies to professional armies, the rise of gunpowder weapons, and the integration of humanist thought into military theory.
-
B.
legendary army
A legendary army is a renowned military force whose extraordinary prowess, historic victories, and enduring reputation elevate it to near-mythic status in collective memory.
-
C.
military event
A military event is an occurrence involving organized armed forces engaging in actions such as combat, maneuvers, operations, or strategic activities within a specific time and place.
-
D.
military history
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
-
E.
militaristic civilization
A militaristic civilization is a society whose culture, economy, and governance are heavily oriented around warfare, military values, and the maintenance or expansion of power through armed force.
- 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.