Triple
T33395514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Skies Treaty |
E855159
|
entity |
| Predicate | statusOfRussia |
P198682
|
FINISHED |
| Object | withdrew from treaty |
—
|
LITERAL FINISHED |
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: withdrew from treaty | Statement: [Open Skies Treaty, statusOfRussia, withdrew from treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfRussia Context triple: [Open Skies Treaty, statusOfRussia, withdrew from treaty]
-
A.
statusInRussia
Indicates the legal, social, or operational condition or standing that something or someone has specifically within the context of Russia.
-
B.
legalStatusClaimedByRussia
Indicates that Russia asserts a particular legal status or claim over the referenced entity or territory.
-
C.
statusInRussianEmpire
Indicates the legal or social standing an entity held within the political and administrative system of the Russian Empire.
-
D.
postSovietStatus
Indicates that an entity has a political, social, or historical status related to the period or conditions following the dissolution of the Soviet Union.
-
E.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
- F. None of above. chosen
Provenance (4 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
| PDg | Predicate description generation | batch_69fefb13eb288190bcfae0541cfd7b98 |
completed | May 9, 2026, 9:15 a.m. |
Created at: May 1, 2026, 1:35 a.m.