Triple
T35871556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Special Monitoring Mission to Ukraine |
E1037238
|
entity |
| Predicate | monitoredAgreement |
P109928
|
FINISHED |
| Object | Minsk Protocol |
—
|
NE NERFINISHED |
How this triple was built (2 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: Minsk Protocol | Statement: [OSCE Special Monitoring Mission to Ukraine, monitoredAgreement, Minsk Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitoredAgreement Context triple: [OSCE Special Monitoring Mission to Ukraine, monitoredAgreement, Minsk Protocol]
-
A.
supervisedAgreement
chosen
Indicates that one entity oversees, validates, or manages the terms and fulfillment of an agreement between parties.
-
B.
requiresAgreementWith
Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified entity.
-
C.
optionalProtocolMonitored
Indicates that monitoring of the specified protocol is supported but not required or always enabled.
-
D.
privacyProtocolsInclude
Indicates that certain privacy protocols encompass, contain, or make use of specified measures, rules, or components.
-
E.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.