Triple
T32538553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian confederation |
E831655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coalition of Roman allies |
C54033
|
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: coalition of Roman allies Context triple: [Italian confederation, instanceOf, coalition of Roman allies]
-
A.
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.
-
B.
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.
-
C.
anti-Roman coalition
An anti-Roman coalition is a temporary or enduring alliance of states, tribes, or factions united primarily by their shared opposition to Roman power, influence, or expansion.
-
D.
Italian allies’ confederation
chosen
A coalition of Italian city-states and regional powers that formed a mutual alliance for defense, political coordination, and the balancing of influence within the Italian peninsula.
-
E.
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.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.