Triple
T19025022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman entry into World War I |
E465587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military alliance decision |
C32214
|
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 decision Context triple: [Ottoman entry into World War I, instanceOf, military alliance decision]
-
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.
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.
-
C.
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.
-
D.
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.
-
E.
international political decision
chosen
An international political decision is a formal choice or policy action made by one or more states or global governing bodies that shapes relations, obligations, or power dynamics across national borders.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.