Triple
T8924985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perusine War |
E212517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal conflict of the Roman Republic |
C25317
|
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: internal conflict of the Roman Republic Context triple: [Perusine War, instanceOf, internal conflict of the Roman Republic]
-
A.
phase of the Roman Republic
A phase of the Roman Republic is a distinct historical period characterized by specific political structures, social dynamics, and key events that collectively shaped the evolution of Roman republican governance.
-
B.
conflict in the Holy Roman Empire
Conflict in the Holy Roman Empire encompasses the political, religious, and territorial struggles among emperors, princes, cities, and external powers that shaped the empire’s fragmented structure and shifting balance of authority.
-
C.
Roman political movement
A Roman political movement is a collective effort by individuals or groups in ancient Rome to influence governance, laws, and public policy in pursuit of specific social, economic, or ideological goals.
-
D.
Punic War
The Punic War is a historical conflict between ancient Rome and Carthage, characterized by a series of three wars fought from 264 to 146 BCE for dominance over the western Mediterranean.
-
E.
Roman political intervention
Roman political intervention refers to the actions and strategies by which Roman authorities, institutions, or influential individuals sought to influence, control, or reshape political processes and power structures within Rome or in foreign states.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:57 p.m.