Triple
T23195899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | refusenik movement |
E579867
|
entity |
| Predicate | opposedRestriction |
P437
|
FINISHED |
| Object | Soviet exit visa system |
—
|
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: Soviet exit visa system | Statement: [refusenik movement, opposedRestriction, Soviet exit visa system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedRestriction Context triple: [refusenik movement, opposedRestriction, Soviet exit visa system]
-
A.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
hadRestrictionsOn
Indicates that one entity imposed or was subject to specific limitations, rules, or constraints regarding another entity or activity.
-
C.
notRestrictedBy
Indicates that something is free from limitations, constraints, or prohibitions imposed by another entity or condition.
-
D.
notableRestriction
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
-
E.
policyRestriction
Indicates that an entity is subject to a limiting rule, condition, or constraint imposed by a policy.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fdb279c81908dcc46f2786a86cd |
completed | April 29, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:06 p.m.