Triple
T5450442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga Federal |
E122355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federalist political and military alliance |
C8966
|
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: federalist political and military alliance Context triple: [Liga Federal, instanceOf, federalist political and military alliance]
-
A.
confederation of states
chosen
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.
-
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 union
A political union is a formal association of two or more political entities that share or merge governance structures to coordinate policies, laws, and collective decision-making.
-
D.
religious and political alliance
A religious and political alliance is a coalition in which faith-based groups and political actors formally or informally coordinate their agendas, resources, and influence to pursue shared ideological, social, or policy goals.
-
E.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:07 p.m.