Triple
T8311943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Populares |
E194610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman political movement |
C24207
|
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 political movement Context triple: [Populares, instanceOf, Roman political movement]
-
A.
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.
-
B.
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.
-
C.
Roman imperial policy
Roman imperial policy refers to the strategies, laws, and administrative practices employed by Roman emperors to maintain control, integrate diverse provinces, manage resources, and project power across the empire.
-
D.
Roman senator
A Roman senator is a high-ranking political figure in ancient Rome who participates in legislative, advisory, and administrative decision-making within the Senate, influencing the governance and policies of the Roman state.
-
E.
client state of the Roman Republic
A client state of the Roman Republic was a formally independent polity that, through treaties or coercion, accepted Roman supremacy in foreign policy, military support, and often internal affairs in exchange for protection and limited autonomy.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.