Triple
T5710127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Trials |
E125884
|
entity |
| Predicate | laterEvent |
P54905
|
FINISHED |
| Object | posthumous rehabilitation of many defendants during Khrushchev Thaw |
—
|
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: posthumous rehabilitation of many defendants during Khrushchev Thaw | Statement: [Moscow Trials, laterEvent, posthumous rehabilitation of many defendants during Khrushchev Thaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEvent Context triple: [Moscow Trials, laterEvent, posthumous rehabilitation of many defendants during Khrushchev Thaw]
-
A.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
B.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
-
C.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
-
D.
laterRelatedEvent
chosen
Indicates that one event is temporally related to another by occurring at a later time.
-
E.
laterPromoter
Indicates that one promoter occurs or becomes active at a later time than another promoter in a regulatory or temporal sequence.
- 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_69c0082d6fe48190b777fb383769e5c8 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c47f4c81909e6849c3be3e951c |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.