Triple
T26681091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franco-Russian Military Convention of 1892 |
E672613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defensive alliance agreement |
C42371
|
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: defensive alliance agreement Context triple: [Franco-Russian Military Convention of 1892, instanceOf, defensive alliance agreement]
-
A.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
-
B.
offensive alliance
An offensive alliance is a coalition of actors that coordinate and commit resources to initiate or escalate aggressive actions against a common target to achieve shared strategic gains.
-
C.
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.
-
D.
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.
-
E.
bilateral military agreement
chosen
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:20 a.m.