Triple

T19483108
Position Surface form Disambiguated ID Type / Status
Subject Jackson–Vanik amendment E487440 entity
Predicate statusForRussia P13676 FINISHED
Object repealed in 2012 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: repealed in 2012 | Statement: [Jackson–Vanik amendment, statusForRussia, repealed in 2012]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusForRussia
Context triple: [Jackson–Vanik amendment, statusForRussia, repealed in 2012]
  • A. statusInRussia chosen
    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. stationingConsideredByRussia
    Indicates that the deployment or positioning of something (e.g., forces, equipment, or assets) is regarded, evaluated, or treated in a particular way by Russia.
  • E. statusInBelarus
    Indicates the legal, social, or official standing or condition that an entity has within the context of Belarus.
  • 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_69d8e8d924388190b847cb15bb3d0aff completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6343c23308190a35f462f95338651 completed April 20, 2026, 2:12 p.m.
PD Predicate disambiguation batch_69e4fd7883308190b73912a71a35a835 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:39 p.m.