Triple
T2055820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman–Germanic wars |
E45671
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient conflict |
C1657
|
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: ancient conflict Context triple: [Roman–Germanic wars, instanceOf, ancient conflict]
-
A.
ancient Greek war
Ancient Greek war encompasses the organized, often city-state-driven conflicts of classical Greece, characterized by hoplite phalanxes, naval battles like those at Salamis, shifting alliances, and a fusion of military, political, and cultural motives.
-
B.
mythological war
A mythological war is a large-scale, often cosmic conflict between gods, heroes, and supernatural beings that explains or symbolizes fundamental cultural, moral, or natural forces within a mythic tradition.
-
C.
series of conflicts
chosen
A series of conflicts is a sequence of interconnected disputes, struggles, or confrontations that unfold over time, often escalating or evolving as parties respond to previous clashes.
-
D.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
E.
succession war
A succession war is an armed conflict triggered by competing claims to a throne or leadership position, typically following the death, deposition, or disputed legitimacy of a ruler.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:40 p.m.