Triple
T6035077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konstantin Berman-Yurin |
E134397
|
entity |
| Predicate | chargeContext |
P1693
|
FINISHED |
| Object | alleged anti-Soviet conspiracies |
—
|
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: alleged anti-Soviet conspiracies | Statement: [Konstantin Berman-Yurin, chargeContext, alleged anti-Soviet conspiracies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeContext Context triple: [Konstantin Berman-Yurin, chargeContext, alleged anti-Soviet conspiracies]
-
A.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
B.
charge
chosen
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
C.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
D.
chargeArrangement
Indicates an agreement or setup specifying how charges, fees, or payments are to be applied or managed between parties.
-
E.
chargeDetail
Indicates a detailed specification of a financial charge, including its components, conditions, or breakdown within a transaction or billing context.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b33a7c8190ad6282286199b192 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.