Triple
T8313575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Triumvirate |
E194648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman political alliance |
C24217
|
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 alliance Context triple: [First Triumvirate, instanceOf, Roman political alliance]
-
A.
ancient Greek alliance
An ancient Greek alliance is a formal coalition of independent city-states that coordinate their military, political, and sometimes economic actions for mutual defense or shared objectives.
-
B.
Catholic military alliance
A Catholic military alliance is a coalition of armed forces from predominantly Catholic states or groups, formed to defend shared religious, political, or territorial interests under a common Catholic identity.
-
C.
political-military alliance
A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
-
D.
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.
-
E.
European political alliance
A European political alliance is a cooperative grouping of political parties or states within Europe that coordinate policies, strategies, and actions to advance shared ideological or strategic interests across national borders.
- 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:55 p.m.