Triple
T26907764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Army (temporary alliances) |
E677301
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military alliance pattern |
C52197
|
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 alliance pattern Context triple: [Red Army (temporary alliances), instanceOf, military alliance pattern]
-
A.
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.
-
B.
participants in military alliance
Participants in a military alliance are sovereign states or entities that formally agree to cooperate in defense and security matters, sharing obligations, resources, and strategic commitments against common threats.
-
C.
multinational military coalition
A multinational military coalition is a temporary or long-term alliance of armed forces from multiple sovereign states that coordinate resources, strategy, and operations to achieve shared security or defense objectives.
-
D.
historical alliance
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural 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. 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6 a.m.