Triple
T7711509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eduard Holtzman |
E174766
|
entity |
| Predicate | accusedPoliticalAlignment |
P78281
|
FINISHED |
| Object | Trotskyist opposition |
—
|
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: Trotskyist opposition | Statement: [Eduard Holtzman, accusedPoliticalAlignment, Trotskyist opposition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accusedPoliticalAlignment Context triple: [Eduard Holtzman, accusedPoliticalAlignment, Trotskyist opposition]
-
A.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
B.
accusedGroup
Indicates that one group is formally charged or blamed by another party for committing a wrongdoing or offense.
-
C.
accusedRank
Indicates that one entity is accused of holding, or being associated with, a particular rank or position.
-
D.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
E.
accusedName
Indicates that a particular person or entity is identified as the one who is accused in an accusation or legal charge.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c702e9a32081909a153190a62af426 |
completed | March 27, 2026, 10:21 p.m. |
Created at: March 27, 2026, 4:04 p.m.