Triple
T28411106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italic Confederation |
E719663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military confederation |
C38100
|
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: military confederation Context triple: [Italic Confederation, instanceOf, military confederation]
-
A.
military confederacy
chosen
A military confederacy is a loose alliance of semi-independent states or groups that coordinate their armed forces and defense policies for mutual security while retaining significant political autonomy.
-
B.
confederation of states
A confederation of states is a union of sovereign states that voluntarily cooperate on certain common matters through a central body that has limited authority and depends on the member states for implementation and enforcement.
-
C.
imperial confederation
An imperial confederation is a loose union of semi-autonomous states or territories under the overarching authority of an empire, which coordinates common policies while allowing substantial local self-rule.
-
D.
noble confederation
A noble confederation is a formal alliance of aristocratic houses or lineages that cooperate for mutual defense, political influence, and the preservation of shared privileges while retaining their individual autonomy.
-
E.
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.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:27 a.m.