Triple
T1017691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Yelchin |
E21968
|
entity |
| Predicate | emigrationReason |
P3057
|
FINISHED |
| Object | antisemitism in Soviet Union |
—
|
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: antisemitism in Soviet Union | Statement: [Viktor Yelchin, emigrationReason, antisemitism in Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emigrationReason Context triple: [Viktor Yelchin, emigrationReason, antisemitism in Soviet Union]
-
A.
reasonForRelocation
chosen
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
-
B.
estimatedEmigrants
Indicates the estimated number of people who have left a place or country to live elsewhere.
-
C.
immigratedTo
Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
-
D.
yearOfEmigration
Indicates the specific year in which an entity permanently left its country or place of origin to settle elsewhere.
-
E.
usedToRestrictEmigrationFrom
Indicates that something was employed as a means to limit or control people leaving a particular place or country.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c4d488819081d8214ba0a22fe5 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.