Triple
T34980785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Cherevin |
E1008807
|
entity |
| Predicate | isCorrupt |
P182163
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Viktor Cherevin, isCorrupt, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCorrupt Context triple: [Viktor Cherevin, isCorrupt, true]
-
A.
corrupts
Indicates that one entity causes another entity, system, or process to become morally, functionally, or structurally degraded or impaired.
-
B.
onCanaryCorruption
Indicates that an entity experiences errors, instability, or data issues specifically in a canary (pre-production or limited-release) environment.
-
C.
corruptedFormOf
Indicates that one form of an expression, word, or name is a distorted, altered, or degraded version derived from another, more original form.
-
D.
hasCorruptedMember
Indicates that an entity includes or is associated with at least one member who is compromised, dishonest, or otherwise corrupted.
-
E.
corruptingForceType
Indicates a type or category of influence that causes moral, ethical, or structural degradation in the affected entity.
- F. None of above. chosen
Provenance (4 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.