Triple
T28411107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italic Confederation |
E719663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-Roman coalition |
C54034
|
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: anti-Roman coalition Context triple: [Italic Confederation, instanceOf, anti-Roman coalition]
-
A.
anti-Venetian coalition
An anti-Venetian coalition is an alliance of states or powers formed to counter, contain, or dismantle the political, economic, or military influence of the Republic of Venice.
-
B.
anti-Bolshevik military coalition
An anti-Bolshevik military coalition is a temporary alliance of armed forces and political groups united to oppose, contain, or overthrow Bolshevik or communist regimes, typically during revolutionary or civil war contexts.
-
C.
Roman political alliance
A Roman political alliance is a formal or informal partnership between individuals, factions, or states in ancient Rome formed to consolidate power, advance mutual political interests, and influence governance and decision-making.
-
D.
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.
-
E.
ancient Roman ally
An ancient Roman ally is a foreign individual, city, or state that entered into a formal relationship with Rome—often through treaties or agreements—providing military or political support in exchange for protection, privileges, or 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:27 a.m.