Triple
T20332897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Moscow ceasefire agreement on Idlib |
E492528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russia–Turkey 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: Russia–Turkey agreement Context triple: [2020 Moscow ceasefire agreement on Idlib, instanceOf, Russia–Turkey agreement]
-
A.
Sudanese political agreement
A Sudanese political agreement is a formal accord between Sudanese political actors or factions that outlines shared principles, power arrangements, and mechanisms for governance, conflict resolution, or transition.
-
B.
India–Russia military cooperation activity
India–Russia military cooperation activity encompasses the joint defense initiatives, arms trade, technology transfers, training exercises, and strategic collaborations undertaken between India and Russia to enhance their mutual security and military capabilities.
-
C.
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.
-
D.
arms deal
An arms deal is a transaction involving the sale, transfer, or exchange of weapons and military equipment between parties, often states, organizations, or private entities.
-
E.
treaty
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:22 a.m.