Triple
T22370213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irina Arkadina |
E553018
|
entity |
| Predicate | devalues |
P147399
|
FINISHED |
| Object | Konstantin Treplev’s writing |
—
|
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: Konstantin Treplev’s writing | Statement: [Irina Arkadina, devalues, Konstantin Treplev’s writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devalues Context triple: [Irina Arkadina, devalues, Konstantin Treplev’s writing]
-
A.
wasDevaluedIn
Indicates that the value or worth of an entity was reduced during a specified event, time period, or context.
-
B.
demotes
Indicates that one entity reduces another entity’s rank, status, or level within a hierarchy or system.
-
C.
decline
Indicates a decrease or reduction in the level, amount, quality, or intensity of something over time.
-
D.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
E.
deconstructs
Indicates that one entity systematically takes apart, analyzes, or dismantles another entity or its structure into constituent elements.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158032b748190ad36c7e3809304e9 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.