Triple
T31085755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Malinovsky |
E792228
|
entity |
| Predicate | consequenceOfExposure |
P812
|
FINISHED |
| Object | resignation from the Duma |
—
|
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: resignation from the Duma | Statement: [Roman Malinovsky, consequenceOfExposure, resignation from the Duma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfExposure Context triple: [Roman Malinovsky, consequenceOfExposure, resignation from the Duma]
-
A.
resultOfExposure
Indicates that something occurs or exists as a consequence of being exposed to a particular agent, condition, or environment.
-
B.
routeOfExposure
Indicates the pathway or method by which an agent, substance, or factor comes into contact with or enters an organism or system.
-
C.
consequenceOfInjury
Indicates that one event, condition, or outcome occurs as a direct result of a specified injury.
-
D.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
E.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 29, 2026, 9:02 p.m.