Triple
T21567608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шанхайская пятёрка |
E532201
|
entity |
| Predicate | основнойДокумент |
P29960
|
FINISHED |
| Object | Соглашение об укреплении доверия в военной области в приграничных районах 1996 года |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Соглашение об укреплении доверия в военной области в приграничных районах 1996 года | Statement: [Шанхайская пятёрка, основнойДокумент, Соглашение об укреплении доверия в военной области в приграничных районах 1996 года]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Соглашение об укреплении доверия в военной области в приграничных районах 1996 года Context triple: [Шанхайская пятёрка, основнойДокумент, Соглашение об укреплении доверия в военной области в приграничных районах 1996 года]
-
A.
1996 Agreement on Confidence-Building Measures in the Military Field along the LAC
chosen
The 1996 Agreement on Confidence-Building Measures in the Military Field along the LAC is a bilateral India–China accord aimed at reducing the risk of armed conflict and enhancing transparency and restraint in military activities along their disputed Line of Actual Control.
-
B.
Interim Agreement on Offensive Arms
The Interim Agreement on Offensive Arms was a 1972 U.S.–Soviet arms control treaty that placed limits on strategic ballistic missile arsenals as part of the early Cold War nuclear détente.
-
C.
Moscow Agreement on a Ceasefire and Separation of Forces (1994)
The Moscow Agreement on a Ceasefire and Separation of Forces (1994) is a Russia-brokered accord that halted active hostilities between Georgian and Abkhaz forces and established security and separation arrangements monitored by peacekeepers.
-
D.
Minsk Protocol
The Minsk Protocol is a 2014 ceasefire agreement aimed at halting fighting in eastern Ukraine between Ukrainian forces and Russian-backed separatists.
-
E.
Treaty establishing the Regional Security System
The Treaty establishing the Regional Security System is the foundational international agreement that created and governs the Eastern Caribbean’s collective defense and security alliance among participating states.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: основнойДокумент Context triple: [Шанхайская пятёрка, основнойДокумент, Соглашение об укреплении доверия в военной области в приграничных районах 1996 года]
-
A.
majorDocument
chosen
Indicates that a document holds primary or significant importance within a given context or collection.
-
B.
publicDocument
Indicates that a document is officially available to the general public without access restrictions.
-
C.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
D.
regulatoryDocument
Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
-
E.
foundingDocument
Indicates that one entity serves as the official charter, constitution, or primary legal/organizational document that establishes or defines the other entity.
- F. None of above.
Provenance (3 batches)
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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9c9f264819085b4807923860793 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.